Topic on Extension talk:Lockdown

Fixed in the repo. Either clone latest REL_27 code or download the software from the extension distributor for the MW 1.27 branch. // Earlier versions of this exension's code will not work with MW 1.27+

I recently updated MW to the latest commits (it was 1.27 from late 2015). Since than Lockdown is causing very strage permission behavior, apparently it does not recognize the different between logged users and anonymous users (i.e - logged-on sysop cannot edit MW namespace pages, logged users cannot edit etc.

Facing the same situation. Maybe there's a change in recent commits regarding user permissions?

I suspect that this is what I described in task T137051. To sum up: Lockdown is not compatible with MW 1.27 yet.

Did the fix Lockdown: 0d59ae7a7e0e3eb5a4638ba8f814a57926dada42 work?

No, unfortunately not.

Is somebody going to fix it?

At the moment, when I want to mange user rights, I had to disable the Lockdown extension.

I need it however to protect some namespaces from public access,

Hopefully. I am not a coder so I cannot do it. Keeping fingers crossed.

I think I have a fix.

Using the version from git master, file Lockdown.php dated 31-may-2016, I replaced

in function function lockdownSearchableNamespaces($arr) {

the line

//if ( $user->getId() === null && $user->getName() === null ) {

with

if ( $user->getId() === null || $user->getName() === null || $user->getName() == '' ) {

I do not claim to understand it, but it resolves the problem that the extension locks out users from editing, who normally have the permission to edit.

im still seeing the problem that i cant add or edit permissions for users as a sysop, even after applying the change above :/

I have uploaded a patch set suggested by a user which at least restores functionality: gerrit. I dunno if it gets through though. The current status on this issue is however always visible on phabricator.

REL1_27 has now been fixed with a patch from Javawookie. Thanks a lot.