Last modified: 2014-08-09 16:56:04 UTC
Things like $wgSysopUserBans, $wgSysopRangeBans, $wgSysopEmailBans (and any similar ones?) should be phased out, turned into proper rights for $wgGroupPermissions and considered deprecated.
Making the changes isn't difficult. Just how the hell do we go about deprecating globals, making sure they work for x future versions (yay, backcompat :/)..? Or do we just do it, and mark it in the release notes as a breaking change? (How many of these are used in extensions [Not looked myself, as I'm venting, whilst procrastinating from sleep])
Or would we do something like $blah = false; if ( $wgUser->isAllowed( 'blahaction' ) ) { $blah = true; } else { global $wgBlahAction; if ( isset( $wgBlahAction ) && $wgBlahAction ) { //Maybe whinge about being deprecated $blah = true; } } if ( $blah ) { //Do/allow optional shizz here }
Ping, Chad?
We should come up with a solution like the one in Comment 2 for reducing the globals Bug #9968
Most of Setup.php is configuration B/C; I think we probably need a clear-out and documentation blitz in there.
(In reply to Chad H. from comment #0) > Things like $wgSysopUserBans, $wgSysopRangeBans, $wgSysopEmailBans (and any Only one remaining is $wgSysopEmailBans.