some users/usergroup issues in revo2.0.8?

Hi,

i’m trying to figure out the best way to set up limited manager permissions.
i have created an admin-user role with admin-lite access policy and when i assign a user to the Administrator Group with this admin-user role it all works ok.
However i have just started to look at modifying the Manager further (as i would with MM in Evo) but see in the Form Customization i have to assign a User Group to distinguish how users will view the Manager. For example if i create a new Profile and don’t select a User Group the changes affect all users and i want the overall admin to be able to view everything and only the users with admin-user roles have their Manager area display changed.

So i created an Editor-UG user group with a role of ’admin-user’ and policy of ’admin-lite’ with ’admin-lite’ set in the context access but when i login again the left hand document tree cannot be seen. I don’t understand this as i thought it was the access policy that defined what functions can be carried out in the Manager and this has not changed from when the same user was placed in the ’Administrator’ user group.

What could be wrong here?

I know there is a learning curve and i am slowly trying to get to grips with this side of Revo but an example of the tasks that would be commonplace in Evo’s ManagerManager would be a great help.

Thanks for any help

J

You’re not required to select a user group for form customization rules. If you don’t select a group, the rule will apply to all users.

hi and thanks for the quick reply.
That’s my point but perhaps didn’t explain it very well. I don’t want to apply the rules to all users, I only want them to apply to the ’admin-user’ role (admin-lite access policy) to simplify their Manager view. Am i right that in this instance i would have to assign a User Group?
If that is right then i have created a user group ’ Editor-UG’ so i now have 2 user groups, ’Administrator’ and ’Editor-UG’ and i have placed my test-user (having ’admin-user’ role and ’admin-lite’ policy) in the Editor-UG user group. The problem is when i now access the Manager with the test-user the document tree does not display but it did when this same user was in the ’Administrator’ user group!
Hope that makes sense.

Thanks

Did you give the Editor user group a Context Access ACL entry for the Web context? They need one in order to see the tree.

Hi,

I’ve attached a screen shot of what i have in the contexts for my Editor-UG user group. To be honest i’m still not fully clued up about what contexts actually do so am not entirely sure if i’m doing this correctly, so would gladly accept any help here.
I’ve added contexts for mgr and web with ’admin-user-10’ and ’admin-lite’ access policy which is the same as for the Administrator user group context (although the administrator UG also has other contexts associated with it).
Even now i’ve added the web context the document tree is not displaying and i also still cannot logout.

Do i need to add more contexts?

No, that’s the right number of contexts, assuming that you haven’t created any other front-end contexts in the Resource tree.

Check the admin-lite policy to make sure that it’s based on the Administrator template and that all the necessary permissions (e.g. resource_tree) are checked.

As far as i can see i have everything in the Editor-UG the same as the Administrator, when i assign the user to the Admin group the Manager looks as expected which i guess suggests there is a difference:-/
I don’t know why it isn’t working but if you can suggest anything else i’d be grateful.
Failing that I may have to revisit Revo another time as i’m having too many issues and the learning curve beyond the basic templating seems much bigger than i’d anticipated.

Cheers

I’d go to the admin-lite policy and put a checkmark next to every permission. Assuming that that solves things, start unchecking them a few at a time and see which ones cause trouble when they’re unchecked.

You’ve probably done this, but if not, delete all the files in the core/cache directory, flush permissions and sessions, clear your browser cache and cookies, and log back in.