Last modified: 2012-09-19 18:13:59 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 T33225, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 31225 - Message "protect-level-autoconfirmed"/"protect-level-sysop" should be used instead of "protect-fallback"
Message "protect-level-autoconfirmed"/"protect-level-sysop" should be used in...
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Language setup (Other open bugs)
unspecified
All All
: Highest major (vote)
: ---
Assigned To: Nobody - You can work on this!
http://www.mediawiki.org/wiki/Sandbox...
: i18n
Depends on:
Blocks: 29068
  Show dependency tree / graph
 
Reported: 2011-09-28 20:17 UTC by Krinkle
Modified: 2012-09-19 18:13 UTC (History)
2 users (show)

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

Attachments
The bug on mw.org (281.54 KB, image/png)
2011-09-28 20:17 UTC, Krinkle 		Details
Working fine on 1.19-alpha (49.80 KB, image/png)
2011-09-28 20:18 UTC, Krinkle 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Krinkle 2011-09-28 20:17:10 UTC 
When going to the protect action on any 1.18wmf1-wiki, MediaWiki fails to find the message for the special 'sysop' case.


This results in the interface being rendered with 'protect-fallback' instead which, as it should, assumes that the passed variable is a user right. However, sysop (which is internally mapped to 'protect' && 'editprotected'), is a user group and should have (and does have) a special dedicated interface message.

This works correctly for me in the development trunk, but on nl.wikipedia.org and mediawiki.org this is currently failing. Perhaps something wrong with the localization ? Or a bug that was fixed but not backported from 1.19 to 1.18 ?
Comment 1 Krinkle 2011-09-28 20:17:37 UTC 
Created attachment 9116 [details]
The bug on mw.org
Comment 2 Krinkle 2011-09-28 20:18:16 UTC 
Created attachment 9117 [details]
Working fine on 1.19-alpha
Comment 3 Aaron Schulz 2011-10-01 05:29:42 UTC 
Any idea what rev fixed this?
Comment 4 Aaron Schulz 2011-10-01 05:41:21 UTC 
Fixed in r94761. Backported and live now.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links