Author: mike.lifeguard+bugs
Description:
The form at Special:Block hides the other field when you use it - global blocking should do the same.
The local block form also has a dropdown of predefined block reasons - global blocking should do the same.
Please also match the default MediaWiki:Globalblocking-block-intro to MediaWiki:Blockiptext.
Version: unspecified
Severity: enhancement
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Invalid | None | T40638 [DO NOT USE] Interface messages needing rewording or documentation and other issues with existing messages [superseded by #Voice_&_Tone] | ||
| Resolved | None | T20098 MediaWiki:Globalblocking-block-intro should match MediaWiki:Blockiptext | ||
| Resolved | PiRSquared17 | T40367 MediaWiki:Globalblocking-blocked should tell the IP range | ||
| · · · |
(In reply to comment #0)
The form at Special:Block hides the other field when you use it - global
blocking should do the same.
Reported separately at bug 18412.
mike.lifeguard+bugs wrote:
(In reply to comment #0)
The local block form also has a dropdown of predefined block reasons - global
blocking should do the same.
See bug 18413
Please also match the default MediaWiki:Globalblocking-block-intro to
MediaWiki:Blockiptext.
Changing the summary to leave this as the only request for this bug.
mike.lifeguard+bugs wrote:
(In reply to comment #3)
Why should it match?
Because these system messages differ only in whether the block is local or global? Of course I don't mean it should be an exact copy - it needs to say that the block will affect all wikis.
But for example, there's no mention of adhering to policy. This makes little difference for Wikimedia, since MediaWiki:Globalblocking-block-intro is only relevant at Meta, and I've already changed the message, but it might matter for third-party users. But as I say, it's utterly trivial.
Marking this bug as Lowest priority.
I've done this in a batch to (usually enhancement request) bugs where:
If you're interested in having one of these bugs fixed, your best bet is to write the patch yourself.
Adding many blockers of bug 38638 to the list of "easy" bugs, to mark them as candidates for [[mw:Google Code-in]] tasks (gci2013). If you think this bug is not suitable, remove the keyword.
I agree. The other remaining request to match the text is declined. Local and global blocking are different things and globalblock-intro is descriptive so IMHO there's no need for that.