I requested this change be made as I run a atest wiki, meant for users to play around with
buttons. All registered users have near-sysop rights by default, however there are several
pages (such as the rules and main page) I wanted to restrict editing of. I added a
protection level higher, but then found that one could simply unprotect the page and edit
it. If this isnt the cleanest way, maybe adding the ability to add other actions to
protect against (e.g. instead of just move and edit, allow protecting delete, protect,
etc) would work. It seems possible with config settings but doesnt work.
Date: Mon, 3 Dec 2007 12:45:41 +1100
Subject: Re: [Wikitech-l] [MediaWiki-CVS] SVN:  trunk/phase3
On 12/1/07, werdna(a)svn.wikimedia.org
Date: 2007-12-01 09:08:43 +0000 (Sat, 01 Dec 2007)
* (bug 11346) Prevent users who cannot edit a page from changing its restrictions.
This kind of hard-coded merging of restrictions makes me uneasy. What
if someone wants to have a protection level where no one at all can
edit the page, without explicitly unprotecting? Then no one could
ever unprotect it . . .
That's a rather unlikely scenario.
In general, I like to see "edit" mean
not "edit and also unprotect, if you have the unprotect right". But
maybe that's just me.
A cleaner way to do this, if protection levels higher than sysop are
desired, is to explicitly have different levels of the 'protect'
permission. This is possibly most suitable for an extension.
It may be unclean, but it does make MediaWiki slightly easier to
configure, by removing a possible pitfall.
-- Tim Starling
Wikitech-l mailing list
Express yourself instantly with MSN Messenger! Download today it's FREE!