Last modified: 2011-03-13 18:05: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 11422 - Cascading protection and MediaWiki space
Cascading protection and MediaWiki space
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.11.x
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-09-22 07:59 UTC by Nilfanion
Modified: 2011-03-13 18:05 UTC (History)
3 users (show)

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


Attachments

Description Nilfanion 2007-09-22 07:59:37 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.
Comment 1 Aaron Schulz 2007-09-22 10:45:54 UTC
why not resolve the template into highest level wikitext and put it in? That is also more efficient.
Comment 2 Nilfanion 2007-09-22 13:41:21 UTC
(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 ;)



Comment 3 Platonides 2007-09-22 13:51:05 UTC
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)

Comment 4 Andrew Garrett 2008-08-08 11:54:49 UTC
Considering marking this bug as WONTFIX. Comments?
Comment 5 Aaron Schulz 2008-09-07 20:52:08 UTC
(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.

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


Navigation
Links