Last modified: 2014-08-18 04:55:31 UTC
When attempting to duplicate bug 36282 it was discovered that members of a user group with the 'protect' user right, and sufficient rights to edit through at least one level of protection, were unable to issue protection up to the highest level they were able to edit. To replicate: 1. In LocalSettings.php, add the following lines. These should replace the default protection levels with one called "level1" and another "level2". It also creates a new user group called "level1editor" that is allowed to edit "level1" protected pages and place protection on pages up to "level1": $wgRestrictionLevels = array('', 'level1', 'level2'); $wgGroupPermissions['level1editor']['level1'] = true; $wgGroupPermissions['level1editor']['protect'] = true; $wgGroupPermissions['sysop']['level1'] = true; $wgGroupPermissions['sysop']['level2'] = true; 2. Log into a bureaucrat account. Give yourself +sysop and +level1editor. 3. Go to a random page and ensure you can issue all levels of protection. 4. Go back to Special:Userrights and remove your sysop flag. 5. Go back to the page you looked at before. The "protect" or "change protection" tab should no longer be present. For more information, see comments on bug 36282.
To clarify, are these the exact steps you mean: 1. Create a group "level1editor" with the "level1" and "protect" permissions. 2. Create a group "sysop" with the "level1", "level2", and "protect" permissions. 3. As a sysop, protect a page using level2 protection. 4. As a level1editor, attempt to change protection of the aforementioned page. If so, then I'm not sure what the bug is. Currently pages can only be protected using one level of protection at a time (meaning they cannot be simultaneously level1 and level2 protected). So if a page is level2 protected, and you're only a level1editor, you shouldn't have permissions to change protection of that page. And I've found this is exactly what happens.
Hersfold, are you still experiencing this bug? As Tyler Romeo notes above, I'm not sure what the ticket is for, and the current behavior seems to be as intended.
Hersfold, can you please answer comment 2?
Unfortunately closing this report as no further information has been provided. Hersfold: Please feel free to reopen this report if you can provide the information asked for in comment 2 and comment 3, and if this still happens. Thanks!
