Last modified: 2011-03-13 18:05:12 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 14002 - Add $2 to MediaWiki:Cascadeprotectedwarning
Add $2 to MediaWiki:Cascadeprotectedwarning
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch, patch-need-review
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-06 21:20 UTC by MZMcBride
Modified: 2011-03-13 18:05 UTC (History)
2 users (show)

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


Attachments
Cascadeprotectedwarning patch (2.36 KB, patch)
2008-05-06 22:17 UTC, Alex Z.
Details

Description MZMcBride 2008-05-06 21:20:14 UTC
MediaWiki:Cascadeprotected has a $2 parameter (listing the pages that are protected), however, MediaWiki:Cascadeprotectedwarning does not.
Comment 1 Alex Z. 2008-05-06 22:17:35 UTC
Created attachment 4884 [details]
Cascadeprotectedwarning patch

Make Cascadeprotectedwarning work more like Cascadeprotected.
Comment 2 Andrew Garrett 2008-08-08 10:43:18 UTC
FIXED in r38879, not with the provided patch.
Comment 3 Brion Vibber 2008-08-08 21:57:23 UTC
Reverted r38879, r38880  in r38958.

Incompatible change to message, and just seems kind of ugly. It's usually easier to maintain the core message without having to remember to slap "and the bit that always follows it" on the end every time.

Probably the other message referred to should be fixed to follow general conventions, rather than this one changed to break them. :)

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


Navigation
Links