Last modified: 2013-01-14 21:48:22 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 <https://commons.wikimedia.org/w/index.php?title=File:17W_Aug_14_1996_0124Z.png&action=history> which is included in <http://commons.wikimedia.org/w/index.php?title=Main_Page&action=history>, but it didn't work too well.
Are there any other solutions to this problem that I might have overlooked?
-- Tomasz (odder)
I would suggest applying cascading protection to a file's upload permission only.