Last modified: 2014-11-18 18:07:17 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 3345 - Special:BlockList search doesn't find autoblocks
Special:BlockList search doesn't find autoblocks
Status: NEW
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
unspecified
All All
: Normal enhancement with 9 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 4618
  Show dependency treegraph
 
Reported: 2005-09-03 14:59 UTC by p_simoons
Modified: 2014-11-18 18:07 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description p_simoons 2005-09-03 14:59:02 UTC
When searching for User:Foo on Special:Ipblocklist, the search should also turn
up items like "User:Admin blocked #478932473, autoblocked because IP was
recently used by User:Foo" - because if you're looking for someone to unblock,
you may also need to unblock their IP.

I would also like to be able to search for all non-infinite blocks, or all
infinite blocks.
Comment 1 Chris McKenna 2005-12-26 15:56:07 UTC
I have just submitted a new bug related to the second part of your request -
bug:4391
Comment 2 lɛʁi לערי ריינהארט 2006-01-15 23:56:38 UTC
(In reply to comment #1)
> I have just submitted a new bug related to the second part of your request -
> bug:4391

bug:4391 is
Bug 4391: Filters on Special:Ipblocklist by blocktype
Comment 3 Aaron Schulz 2006-12-02 18:04:09 UTC
Autoblocks do not store the orginal user ID, just 0 (a dummy number for an IP or
non-user). The only way to do this might be to play around with block reason
parsing, which is fairly hackish.
Comment 4 User:JesseW 2006-12-03 21:06:08 UTC
That does seems like a big problem with implementing this without changing the
db structure, but might such a change be possible?  Why don't autoblocks store
the original user id, rather than the dummy value?  It seems like it should be
possible to identify IP blocks by the presence of an IP addr, and store dummy
numbers only for actual direct IP blocks, but let autoblocks be sorted by the
user block they were caused by.  Is this impossible in principle, or is it just
a matter of a large mess to actually get written?
Comment 5 Max Semenik 2008-06-26 15:01:49 UTC
(In reply to comment #3)
> Autoblocks do not store the orginal user ID, just 0 (a dummy number for an IP or
> non-user). The only way to do this might be to play around with block reason
> parsing, which is fairly hackish.

The ID could be stored in ipb_user, because all autoblocks are already explicitly marked in ipb_auto. The only problem here is to check every piece of code that works with blocks not to rely on ipb_user = 0.
Comment 6 Mike.lifeguard 2009-03-15 23:54:45 UTC
It'd be *really* nice to clean up handling of autoblocks - this is viewed as voodoo by most admins & being able to find them would be a good step forward.
Comment 7 db [inactive,noenotif] 2012-10-27 18:32:14 UTC
bug 5445 is fixed, so this maybe not needed, because the autoblock is removed automatically when unblocking

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links