Cascade-protecting files should protect the file, not the description page

Assigned To
Blocked By
T8579: Allowing protecting files without protecting image pages
SJu, Meno25, Nemo_bis and 3 others
"Yellow Medal" token, awarded by Steinsplitter."Yellow Medal" token, awarded by Ciencia_Al_Poder.


Currently inlining an image on a cascade-protected page protects the image, which is good. Bug 6579 introduces functionality that allows only the file to be protected, not the description page. Only changes which actually affect the cascade-protected page should be prevented, which in this case means changing the file pointed to. So cascade protection of inlined images should be to protect the file, not the description page.

Version: unspecified
Severity: normal

bzimport added a subscriber: Unknown Object (MLST).
bzimport set Reference to bz22521.
bzimport created this task.Via LegacyFeb 14 2010, 6:58 PM
ToAruShiroiNeko added a comment.Via ConduitApr 20 2012, 5:27 PM


I feel cascade protection is a problem for Commons where it is impossible to modify the file description page of the highlighted file.

This prevents possible improvements such as categorization of the file, translation of file description, update of assessments template (to match WMF blog).

bzimport added a comment.Via ConduitApr 20 2012, 6:17 PM

saibotrash wrote:

The cascade protection may be used to protect the file descs, too. I think it would be stupid if the behavior would change after several years (for some users).

Maybe a new option should be there: "except file descs from cascade protection"([edit=<unaffected>] just move and upload cascaded). The cascade protection only would need to apply to upload and move.

Ciencia_Al_Poder added a comment.Via ConduitApr 20 2012, 7:27 PM

Saibo: The reason for cascade protection existence is to protect the page and everything that it's included on the page from being changed. Templates are protected because their contents are transcluded on the page. Since editing the template would change the contents of the article, cascade protection prevents the edition of the template contents. For images/files, what it's included in the page is the image itself, not the description, so the upload or revert of versions of the image should be prevented. Uploading a new version of a file is like editing a transcluded template. There's no point in prevent the edition of the file description since editing it won't affect the protected page in any way.

If you want file descriptions to be protected just transclude them on the protected page, like {{:File:Example.png}}. That would be consistent with other namespaces. Otherwise I don't see any point in using cascade protect just for file description pages.

Ciencia_Al_Poder awarded a token.Via WebDec 31 2014, 3:54 PM
Steinsplitter awarded a token.Via WebJan 2 2015, 5:29 PM
SJu added a subscriber: SJu.Via WebSat, Jul 11, 2:49 AM

Add Comment