Problem with user management

Hi,

I have a problem with my user management in 2.1.3-pl

I have secured some sites so they are only visible to users who are logged in. This works fine.

But I can't edit the users as admin in the manager - I can open the user, but the buttons in the upper right corner for saving and so on are missing, and all entries on the first tab (information) and on the third tab (access rights - to which group does the user belong) are empty.

I can put them into groups via security::access control, and it works for the users - but I cannot edit them.

I tried creating a second admin (super user), which worked, but this one can't edit the users as well.

I assume the super users misses some rights to edit the web users, but I don't know why, as IMO a super user should have the possibility to edit everything.

Maybe I have messed up something in the access controls, as I built the member area in the web context - can someone help me out of this mess?

Cheers
Frisco

I think it's more likely that you have a corrupted cache, file, or DB table rather than an error in your access controls (I could be wrong).

The first thing to try is flushing sessions and permissions, deleting all files in the core/cache directory, and clearing your browser cache and cookies.

Upgrading to 2.1.5 might also help.

Hi BobRay,

I tried everything you suggested, including the upgrade, but none worked. I tried disabling FURL (under lighttpd), clearing browser cache and core/cache, but without success.

I disabled FURLs because logging into the manager takes over a minute, look at the time stamps:



and I thought maybe the problem is connected to that. After logging in the manager is fast (with disabled browser cache all the time), but still super users (two of them) can only edit each super user, but not the "web users".

Password changes of the web users via the login snippet on the web site can be done.

Any clues what I could try now?

Maybe the super users are really missing some access rights, or the web or anonymous users need to be configured another way?

Cheers
Frisco

Make sure the ACL entry that gives admin Super Users access to the mgr context is based on the Administrator policy and that policy has every box checked. Also, make sure that they have the role of Super User in the Administrator user group.

It is starting to sound like a bug, though.

I'm not sure if I got you right according the policies. If I edit the admin group, I see:



So the admin group should have all rights in both contexts, right?

And both admin users have:


Is that what you ment?

Ah, to track down if it has to do with FURL/redirection, could you tell me how your manager URL behind the tld looks like? Is it like:
/manager/index.php?a=49 or /manager?a=49 (without index.php)?

I filed Bug #6491 - could you have a look if I did it right?

Frisco [ed. note: Frisco last edited this post 14 years, 9 months ago.]

Looks good, but check the administrator *policy* to make sure all permissions are checked.

This looks fine:

Administrator
Context administration policy with all permissions.
AdministratorTemplate
130 von 130

I edited this policy (unchecking/checking some items again, hoping this might clean things up), saved it, flushed cache and permissions, but unfortunatly nothing changed, I still can't edit web users.

I read the release.txt for 2.2.0 release candidates, there are some bugs fixed which sound like they could have to do something with my problem - so maybe I should wait for 2.2.0-pl being released, maybe an upgrade to this would fix my problems (still hoping) ;-)

As I run a productive site, I don't want to upgrade to a release candidate - and I should double check if all of my needed snippets would be available for this release.

Do you know of API changes from 2.1.5 to 2.2.0 - I have some self made snippets which rely on the API for storing date in extended user fields?

Frisco

I haven't really had time to look at 2.2.