Le 21.6.2008 5:17, « aaron(a)svn.wikimedia.org » <aaron(a)svn.wikimedia.org> a
écrit :
Revision: 36519
Author: aaron
Date: 2008-06-21 03:17:35 +0000 (Sat, 21 Jun 2008)
Log Message:
-----------
* Revert r36478; I don't see the point in this cryptic code
* Restore r36273 as explain on mailing list
Modified Paths:
--------------
trunk/phase3/includes/Article.php
trunk/phase3/includes/ProtectionForm.php
trunk/phase3/includes/Title.php
The problem is that if you want to introduce a new protection level (e.g.
userrights to allow only bureaucrats to edit that page) and that all groups
that have this right also have the "protect" right (wich is correct if you
give bureaucrats the protect right), then you should be able to use cascade
protection for this level. Note that the protection level should be an
right, and not a group (execpt for "sysop" kept for b/c) and it's why
there's an loop on $wgGroupPermission (see also Simetrical's message on
brion's revert of r36273).
This code only allows cascade with the protect level, for a normal install,
it works as expected, but for custom levels (as I mentionned before), it
doesn't work as only can have cascade on one level so I really don't see the
point to have "protect" hardcoded in that check.
--ialex