Problem with users (modifying, logging in)

Latest (r4660) from the SVN. Working decently but can’t create users that actually work.
- Can create a user, and save.
- Can open user for editing, but cannot save. Get error: "User not found!"
- User cannot login to manager (kind of). On login to manager, you get "ArrayArray" displayed, view source to get:

Doesn’t seem to make a difference what role the user has. Everything is basically default on the MODx install; haven’t tweaked any permissions or groups or roles or settings. LAMP server (CentOS 4.6, PHP 5.2.8, MySQL 5.0.x, Apache 2). XCache is disabled. I have run setup a few times while attempting to troubleshoot this and other issues, and based on the error below perhaps that caused some problems.

In the error log I’m seeing:


The initial user (id 1) that’s created on setup works fine. Thoughts?

Brett:

Sorry it took so long to get back to you on this one. This is a problem where the interface has not caught up with the code, and that is being worked on. Basically, the default access permissions for the mgr and connector contexts are assigned with an authority of 0 and in order to get access to the policy attributes attached to these contexts, you not only have to be a member of the Administrator group, but you must also have an authority level of 0. Let me try to explain...

When you create new users in the Administrator group, they are automatically assigned a role in that group called Member vs. the default admin user, which is given a role of SuperUser. These roles define an authority level (the lower the number, the greater the authority), with the default Member role at 9999 and SuperUser at 0. The problem is, at the moment, there is no way to set the users role within a group in the interface. This is not user roles as we know them in 0.9.x, but rather a membership role that a user has within a specific group, allowing for more granular security models; for instance, group administration features can easily be secured from regular members.

To get around this for now, simply edit the access permissions and give them an authority of 9999, or even better, duplicate the existing ACLs for mgr and connector with 9999 authority levels to avoid having to redo this everytime you update before the interface is available to edit user memberships and specify their role in each group.

I’ll fix the manager interface to react better when a user has no access to the mgr/connector contexts in the meantime.

Thx for that, Jason. Figured it was something like that.