Last modified: 2011-05-15 10:02:55 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T19438, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 17438 - Do not show option "Block anonymous users only" if the user to be blocked is registered (if given in URL)
Do not show option "Block anonymous users only" if the user to be blocked is ...
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
unspecified
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org/wiki/Special:...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-10 18:10 UTC by Melancholie
Modified: 2011-05-15 10:02 UTC (History)
3 users (show)

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


Attachments

Description Melancholie 2009-02-10 18:10:10 UTC
Do not show the option "Block anonymous users only" (first checkbox) if the user to be blocked is a registered one (no IP).
That option anyway makes only sense/works for IP addresses.
Comment 1 Andrew Garrett 2009-02-10 18:12:56 UTC
Works for me.

http://en.wikipedia.org/wiki/Special:Block/Werdna
Comment 2 Melancholie 2009-02-10 18:17:13 UTC
Ah, this is done by JavaScript.
Couldn't there be a proper solution for not even delivering this option?
Comment 3 Mike.lifeguard 2009-02-10 18:20:08 UTC
(In reply to comment #2)
> Ah, this is done by JavaScript.
> Couldn't there be a proper solution for not even delivering this option?
> 

It's done by js so it can be done on the fly as you enter a user to block. I don't think there's a way to do it such that you get this option back if you go to Special:Block/Whatever and then decide to actually block 127.0.0.1 instead. I could be wrong though.
Comment 4 Andrew Garrett 2009-02-10 18:21:33 UTC
It's probably done by site JS, in which case the bug should remain open as it was originally, as not all sites have English Wikipedia's site JS.
Comment 5 Mike.lifeguard 2009-02-10 18:26:03 UTC
(In reply to comment #4)
> It's probably done by site JS, in which case the bug should remain open as it
> was originally, as not all sites have English Wikipedia's site JS.
> 

I don't think so... this works on every wiki I've ever been an admin on.
Comment 6 Melancholie 2009-02-10 18:39:58 UTC
Oh, yes. This works on-the-fly. (I seem to block users too seldom to notice that ;-)
The point why I was wondering was that I used [[als:Spezial:Sperre/Komplexx]], coming from Special:RecentChanges.
Not sure if someone should tweak the behaviour for subpaged special page accesses like that?
Tending to self-close this bug...
Comment 7 Happy-melon 2011-03-23 20:43:44 UTC
This is, as noted, now done in core JavaScript.  You can't customise the form options when the user is still allowed to change the block target; there is currently no reason why an admin can't go to Special:Block/Foo and end up blocking an IP or range.

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


Navigation
Links