Last modified: 2014-11-18 18:07:17 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
I have just submitted a new bug related to the second part of your request -
(In reply to comment #1)
> I have just submitted a new bug related to the second part of your request -
Bug 4391: Filters on Special:Ipblocklist by blocktype
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.
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?
(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.
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.
bug 5445 is fixed, so this maybe not needed, because the autoblock is removed automatically when unblocking