Last modified: 2011-03-13 18:05:49 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 14627 - Cascading protection doesn't work for custom user levels
Cascading protection doesn't work for custom user levels
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Page protection (Other open bugs)
1.13.x
All All
: Lowest normal with 4 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-23 22:31 UTC by Matt W.
Modified: 2011-03-13 18:05 UTC (History)
4 users (show)

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


Attachments

Description Matt W. 2008-06-23 22:31:11 UTC
The custom level code is 
<pre>$wgGroupPermissions['steward']['steward'] = true;
$wgGroupPermissions['steward']['protect'] = true
$wgGroupPermissions['staff']['steward'] = true;
$wgRestrictionLevels = array( '', 'autoconfirmed', 'sysop', 'steward');
$wgRestrictionTypes = array( 'edit', 'move', 'delete' ); </pre>

When setting protection to [move:steward,edit:sysop,delete:steward, [CASCADING]] the protection works but doesn't cascade.

Please fix, or let me know how to fix.

Thanks,
Mww113
Comment 1 FunPika 2008-06-23 22:38:42 UTC
I think fixing this will require the reversion of r36519. 
Comment 2 Matt W. 2008-06-23 22:41:52 UTC
It would seem so(In reply to comment #1)
> I think fixing this will require the reversion of r36519. 
> 

Judging that               if ($this->mCascade && ($edit_restriction != 'protect') &&
 	  	                         !(isset($wgGroupPermissions[$edit_restriction]['protect']) && $wgGroupPermissions[$edit_restriction]['protect'] ) )
 	  	                         $this->mCascade = false;

that was removed from the code, I would think so
Comment 3 FunPika 2008-06-28 22:26:14 UTC
Also, currently you can check the box to cascade, but that only adds a useless protection log entry (if the only change was the failed attempt to add cascade) and not actually sets cascade. 
Comment 4 Radon210 2008-07-02 01:19:39 UTC
If this is not possible, how about a configuration setting instead of dependency on the protect right. It can be something like $wgCascadeRestrictionLevels and the default can be array(sysop);
Comment 5 FunPika 2008-07-02 19:04:56 UTC
Fixing this bug should be as easy as reverting r36519 for now. Although such a setting sounds like a good idea. :) 
Comment 6 Aaron Schulz 2008-09-11 07:08:02 UTC
I don't have the dead [cascade] issue and the JS doesn't let you check it if on as well.

At any rate, this is disabled due to the possibility of people transcluding pages to protect them, without protect rights.

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


Navigation
Links