Last modified: 2011-03-13 18:05:22 UTC
MediaWiki space is only editable by sysops, for obvious reasons. However if a page in template is transcluded into the system message, or if an image is used, it needs to be protected independently. If MediaWiki space was cascading protected then there would be no need to local sysops to manually protect these pages.
why not resolve the template into highest level wikitext and put it in? That is also more efficient.
(In reply to comment #1)
> why not resolve the template into highest level wikitext and put it in? That is
> also more efficient.
Well, I noticed this on MediaWiki:Exif-make-value on en.wp. Is there some conflict with the parser function syntax on Template:Exif-make-value or is it just an oversight by the users who assumed that it had to be done through transclusion? I'd rather not make test edits on WP just to find out which...
As for the general case, sure its more efficient. But as it is possible to transclude unprotected pages into system messages, it may still be worth performing a fix for this bug. Might as well protect people from their own stupidity ;)
Then if i wanted normal users to edit Mediawiki:xxx, i wouldn't be able to allow them to change it via a transcluded template. NOTABUG.
What discourages using templates in Mediawiki: messages is that they don't use the full parser, so they not always work as expected (like http://en.wikipedia.org/w/index.php?title=Template:Exif-make-value&diff=153892393&oldid=153887561)
Considering marking this bug as WONTFIX. Comments?
(In reply to comment #4)
> Considering marking this bug as WONTFIX. Comments?
I'd agree. Looks like complexity creep and performance loss for not enough gain.