Last modified: 2013-01-14 21:48:22 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 42818 - Page-specific protection settings should override cascading protection settings (at least for file description pages)
Page-specific protection settings should override cascading protection settin...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Page protection (Other open bugs)
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: 8575
  Show dependency treegraph
Reported: 2012-12-07 10:25 UTC by Tomasz W. Kozlowski
Modified: 2013-01-14 21:48 UTC (History)
1 user (show)

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


Description Tomasz W. Kozlowski 2012-12-07 10:25:39 UTC
When a template (or a page) is put into another page that has cascading protection turned on, and the settings of the cascading protection are such that [action=edit] and [action=move] are checked for sysops only, non-sysop users are not able to edit the template (or the page) -- and this is the desired behaviour.

However, when you put an image into a page with cascading protection (e.g. the main page of Wikimedia Commons), and this page has such settings that [action=edit] and [action=move] are checked for sysops only, non-sysop users are also not able to edit the file description page -- which in the case of files doesn't make any sense, as the file description page is not /that/ important.

There are two possible solutions that I can think of right now for this problem:
#1: Somehow let the software see the difference between a normal page and a file description page (not sure if this is actually doable);
#2: Let page-specific protection settings override the cascading protection setting (for all pages, not only file description ones).

I just tried doing #2 for <> which is included in <>, but it didn't work too well.

Are there any other solutions to this problem that I might have overlooked?

-- Tomasz (odder)
Comment 1 Phillip Patriakeas 2012-12-07 18:38:54 UTC
I would suggest applying cascading protection to a file's upload permission only.

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