Page MenuHomePhabricator

Do not show option "Block anonymous users only" if the user to be blocked is registered (if given in URL)
Closed, ResolvedPublic

Description

Author: Wiki.Melancholie

Description:
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.


Version: unspecified
Severity: enhancement
URL: http://en.wikipedia.org/wiki/Special:Block/Komplexx

Details

Reference
bz17438

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:25 PM
bzimport set Reference to bz17438.
bzimport added a subscriber: Unknown Object (MLST).

Wiki.Melancholie wrote:

Ah, this is done by JavaScript.
Couldn't there be a proper solution for not even delivering this option?

mike.lifeguard+bugs wrote:

(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.

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.

mike.lifeguard+bugs wrote:

(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.

Wiki.Melancholie wrote:

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...

happy.melon.wiki wrote:

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.