katir
I upgraded to lemming 25. Now my ACL is broken. (small disaster!)
-- I can log in as Admin and I have permissions to read, write, create, upload, delete for all name spaces and pages.
-- User manager plugin appears in perfect order: I see my users with their group assignments.
-- ACL manager plugin appears fine too: I can see all name spaces with their their standard permissions set: Generally for most name spaces they are the same
@All None; @Students Read; @Staff Delete (Public cannot see anything; students can read; staff can do anything for most namespaces)
But now, if any user in group "Students" or group "Staff" logs in.. they will always get permission denied. I have tried deleting the ACL entries for a specific name space and then recreating them... That still did not work. bottom line: only admin has access...
I have a complete back up of the directory before upgrade. What do I do to fix this?
katir
I did that. The Wiki is a complete duplicate of all files I had before. But I discovered the problem or at least a solution: under Lemming 25 I was unable, for example, to have anyone in group "Staff" who had permissions to read-write-create-upload-delete to actually log in and see those namespaces even though user "John" was part of group "Staff"...he was locked out.
But, if I created a new group: "staff" with a lower case initial letter and then assign "staff" permissions for all previous name spaces that had permissions for "Staff" and then went into all the users and changed their groups from "Staff" to "staff" then everything worked. It Took me about 45 minutes of somewhat tedious work to go through, create all new identically named groups with lower case initial letter, while assigning the same permissions to all the same name spaces as before, going down the list namespace "Fish" group "Staff" ... read, write, create, upload... delete that line in the ACL and then add back in a new group: "staff" and assign the same permissions... then go thru all the users (fortunately only about 40 users) and reset their groups to "staff, editor, associate" etc ... all lower case... Now everything works.
Now this is "circumstantial" I'm not saying that "Staff" or "Associate" or "Editor" with upper case first letters might not work, but they did not for me... and by recreating them all I'm good now... It is possible that there was some corruption with the old ACL data and that had I tried to create a new group "Brandnew" with a capital first letter, it may have worked. i.e. possibly the initial capital letter is not a problem... anyway, I'm OK now...