Last modified: 2008-03-09 10:35:59 UTC
The Oversight extension does not define default groups in its code, so installing this extension from svn and changing nothing, results in nobody is able to hide revisions. Furthermore, since on Wikimedia something like $wgGroupPermissions['oversight']['hiderevision'] = true; $wgGroupPermissions['oversight']['oversight'] = true; is used, I think this should be added to HideRevision.php as default group, so it would be also possible to translate the name of that group.
*** Bug 13293 has been marked as a duplicate of this bug. ***
Well, I see no reason why we should avoid this. The only thing to take care of is to update LocalSettings for Wikimedia wikis to avoid double definition of 'oversight' group after it is hardcoded in the Extension code.
Double definition will not be an issue, since both Wikimedia and the defualt will be the same the later (Wikimedia) will just override the former (the default) - and both are identical. It wouldn't hurt to remove it, but I don't see any reason why this is essential.
Honestly, I'm strongly against hardcoding any special groups inside of extensions. I personally get annoyed whenever groups like 'interwiki', 'oversight', 'checkuser', etc... are hardcoded into extensions. I like to use SVN to setup extensions on wiki, which allows be to easily 'svn update' to update the extension. But I have absolutely no need for these extra groups on wiki I've worked on in the past, this kind of stuff has always been something I'd configure as part of a 'staff' group. The extra hardcoded groups just clutters up the groups list with irrelevant and unnecessary groups. And what is really annoying is the fact that since it's hardcoded into the extension, I cannot remove it unless I edit the extension, which voids out my ability to simply 'svn update' anymore and forces me to decide on whether I want to be able to easily update the extension, or I want to remove crap that shouldn't even be hardcoded inside of it. So IMHO, these groups should NOT be hardcoded into extensions. If you absolutely want some sort of hardcoding for these, I recommend creating some sort of file like Oversight-groups.php which can !Optionally! be included into LocalSettings.php if the user really wants the extra groups. It shouldn't be forced on the smaller wiki which don't want them.
(In reply to comment #4) > I like to use SVN to setup extensions on wiki, which allows be to easily 'svn > update' to update the extension. But I have absolutely no need for these extra > groups on wiki I've worked on in the past, this kind of stuff has always been > something I'd configure as part of a 'staff' group. The extra hardcoded groups > just clutters up the groups list with irrelevant and unnecessary groups. And > what is really annoying is the fact that since it's hardcoded into the > extension, I cannot remove it unless I edit the extension, which voids out my > ability to simply 'svn update' anymore and forces me to decide on whether I > want to be able to easily update the extension, or I want to remove crap that > shouldn't even be hardcoded inside of it. unset($wgGroupPermissions['oversight']); Fixed in r31729.
