katir I upgraded our Dokuwiki (Ubuntu 14.* on a Linode Cloud server/instance) to: Release 2017-02-19b "Frusterick Manners" All went well, no issues, but the all users were locked out except admin. They can log in, permissions denied. This also includes and new users who either 1) seek to register... and I (as admin) see them and add to a group 2) if added by me get a message "Permission Denied Sorry, you don't have enough rights to continue" even though they are assigned to a group or groups that have access to one more more name spaces. Strangely, but this could give us a clue... users who had some old cookie or something in their cache could still log in an have access to all pages/namespaces approved for the groups they were in.. but then if they shut down the computer or clear cached (not sure exactly what was being retained) when they tried to go back in, they were now forbidden. Rather serious issue here... especially after we made a decision to use Dokuwiki for ocumentation instead of Google Docs... this initiative promptly fell "flat on it's face" :-/ can anyone help? My user base is small enough i could wipe any ACL settings. and send out a small email blast to register again... though better if they could just log in and see the same name spaces they did before. We are using the "Access Control List Management "page=acl" method... * @ All is set to none * @ user is set to none so I have to add any new user to a group with permission like NameSpace visitor_care:* @hosts .. .. *Create # i.e. anyone assigned as a member of group "hosts" can read|edit|create pages But to say it again, if a new user registers (or I add one from the back end) and I assign them to group "hosts" they are *still* getting permission denied after logging in, even though the ACL should be allowing them to see any pages like /doku.php?id=visitor_care:visitor_calendar Release 2017-02-19b "Frusterick Manners" changed something mission critical that I need to fix...
turnermm Are you doing this manually by editing acl.auth.php? Or are you using the acl configuration manager? And if manually, is this just your short-hand for the setting, "*Create"? Or are you using an asterisk here in acl.auth?
katir I am using the acl configuration manager interface. Sorry there should not have been an * astersk in front of the Create that was meant to represent the radio button "on" state
katir Was working fine before the upgrade and I did not make any changes. I also don't see anything in the Configuration Manager settings that would pertain to this failing now.