Page MenuHomePhabricator

Meta's block reason drop down is the default MediaWiki:Ipbreason-dropdown rather than the local customised file
Closed, ResolvedPublic

Description

With the upgrade to 1.23wmf15 in the past 24 hours, meta's [[m:Special/Block]] reasons in the available drop down have returned to the default. This is despite the file MediaWiki:Ipbreason-dropdown being updated, present and unchanged [https://meta.wikimedia.org/w/index.php?title=MediaWiki:Ipbreason-dropdown&action=history]. Editing the file did not make any difference, nor deleting and undeleting the file.

I have checked enWS (same update schedule, and there is no issue with it picking up the reason's file). My check of the updates for the version only sees mention of an update of the 'docblock'


Version: wmf-deployment
Severity: normal

Details

Reference
bz61945

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:57 AM
bzimport set Reference to bz61945.
bzimport added a subscriber: Unknown Object (MLST).

Oooooh, so thát is the reason why each time I block "Per global block" appears, next to the actual block reason I type in. I also see a blank line where it shouldn't be there. Could someone please fix this asap? It's pretty annoying.

Which language option do you have selected in your preferences?

(In reply to p858snake from comment #2)

Which language option do you have selected in your preferences?

en - English

I've got the same problem on Commons now:

(change visibility) 11:07, 26 February 2014 Trijnstel (talk | contribs | block) blocked Burocraciabrasileira (talk | contribs) with an expiry time of indefinite (account creation blocked, email disabled, cannot edit own talk page) (Uploading unfree files after warnings: Vandalism-only account) (unblock | change block)

(In reply to Trijnstel from comment #3)

(In reply to p858snake from comment #2)

Which language option do you have selected in your preferences?

en - English

Which English are you using?

en-gb for me, and when changing it to straight en, problem resolved.

Plus if I change it at enWS, I can then replicate the issue, so I am happy to say that this is resolved (for me). Well done on that quick resolution identification.

(In reply to billinghurst from comment #6)

en-gb for me, and when changing it to straight en, problem resolved.

Plus if I change it at enWS, I can then replicate the issue, so I am happy
to say that this is resolved (for me). Well done on that quick resolution
identification.

Looks like it is a similar issue to https://bugzilla.wikimedia.org/show_bug.cgi?id=46884 then.

(In reply to p858snake from comment #5)

(In reply to Trijnstel from comment #3)

(In reply to p858snake from comment #2)

Which language option do you have selected in your preferences?

en - English

Which English are you using?

I use the "normal" English. Should I change it to another language too then?

Thanks for taking the time to report this!
This particular problem has already been reported into our bug tracking system, but please feel free to report any further issues you find.

  • This bug has been marked as a duplicate of bug 61942 ***

(In reply to p858snake from comment #7)

(In reply to billinghurst from comment #6)

en-gb for me, and when changing it to straight en, problem resolved.

Plus if I change it at enWS, I can then replicate the issue, so I am happy
to say that this is resolved (for me). Well done on that quick resolution
identification.

Looks like it is a similar issue to
https://bugzilla.wikimedia.org/show_bug.cgi?id=46884 then.

Seem to be. Where is en-strine when you need it. ;-)