I respond to your question on my user talk pages. I do it. Version of AccessControl 2.5 is actively using in our school wiki https://support.dce.felk.cvut.cz is based on MediaWiki 1.20.5 (375d04b) and my wiki https://www.thewoodcraft.org is based on MediaWiki 1.25alpha (b19eec3)
Unfortunately my communication skills in English are not great, thats why I was not able to discuss what one is doing wrong.
Heiya Want, thank you for your reply. I was asking since multiple breaking issues for the code were reported for this extension during the past year. I am puzzled why the extension is working for you. I just spent 2 hours to get it working without success. I have no idea how to interpret the instructions. Perhaps you have a friend with better English skills who could write the instructions. Anyway thanks for your effort creating this extension. Cheers
I don't know, what is wrong for you. I am doing clone of mediawiki core from git, and extension is installed by Manual:Extensions. See important lines from my LocalSettings.php file:
$wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['edit'] = false; require_once( "$IP/extensions/AccessControl/AccessControl.php" ); $wgAccessControlRedirect = true;
These settings were ok. I now successfully got it to work by applying the following patch to "AccessControl.php" on line 151 as described at this spot:
$gt = $Title->makeTitle( 0, $group );
changed to
$gt = $Title->makeTitle( 9998, $group );
I replaced the 0 for the main namespace by the 9998 for the custom access control namespace.
Now things are up and running. Still wondering why it works for you.
The explanation is simple. Extension:AccessControl of the principle does not require custom namespace as somebody wrote in step 2. In older versions of MediaWiki was other detection of namespaces than today. On the talk page is a patch that will allow it but I do not have time do tests that would determine whether if application of it being disruption of functionality or not.
Ah now I get it. So basically the definition of the user groups should happen in the main namespace. Well doing it in a separate one has some appeal but yeah it is the misleading instructions which cause confusion. Thanks as always for your fast reply and thanks a bunch for this extension!
I'm not entirely sure, but I think that the visitor which hasn't access to the namespace where is page with list of members, he not have access to content of page which is protected over extension, although he was on this lists, because his access to page in protected namespace may be denied.
