Access denied while editing resources on multiple context setup

Hi i have a problem after setup multiple context for multiple domains. It gives me Error "Access Denied" error while trying to login on other context and editing the current resources.

Here is my curent setup:

1. Latest Revo 2.2
2. 3 diff Context with 3 diff.. Domains.
3. Duplicated, Renamed and Customized Policies
4. Assign 3 users for each context. (user1,user2 & user3)
5. Created a sample documents / resources for each context.


I check the view_document on my custom policies.

Any idea how to fix this problem?

Thanks & best regards,

Did you ever find an answer to this? I'm having the same problem. I suspect it's just an ACL issue, but I can't figure it out.

Hi aladage,

Even on Newest version of revo 2.2.2 having the same problem, that's why i cannot use the latest Revo for production.
Let's us hope & pray that someone who can help to us.

Is it possible for you to provide a screen of the main tab and acl tab for your screen? Multi contexts is working as far as I know so it's most likely a missed setting.

To be clear, is each user accessing the manager from a completely different domain?

@jay, have to run atm, but will work up some screenshots shortly.

@opengeek: Yes, they are. I think I've told you how I like to do this: for multi-contexts, I usually hack in a switch statement in index.php that initiates the correct context based on http_host. What are you thinking, that I'm maybe just missing a context or user setting or something?

@opengeek: along those lines, a hypothetical question: say down the road, I have a user who needs to access multiple contexts. Would the best approach be to create multiple logins for them, each with separate context access? That seems clunky.

Quote from: aladage at May 16, 2012, 09:51 AM

@opengeek: Yes, they are. I think I've told you how I like to do this: for multi-contexts, I usually hack in a switch statement in index.php that initiates the correct context based on http_host. What are you thinking, that I'm maybe just missing a context or user setting or something?

The index.php should have nothing to do with manager access. Do you mean to say the users you are creating cannot login to the manager? They immediately get "Access Denied"? If so, that is an issue with providing them access to the mgr Context, not any of the front-end Contexts.

Quote from: aladage at May 16, 2012, 09:52 AM

@opengeek: along those lines, a hypothetical question: say down the road, I have a user who needs to access multiple contexts. Would the best approach be to create multiple logins for them, each with separate context access? That seems clunky.

I would provide a separate domain for manager access completely, though they will not be able to view unpublished Resources in domains other than the one they are actually logged into. IOW, for a mgr user logged into foo.bar.com to view unpublished Resources in a Context configured as bar.foo.com, the user would have to either a) physically login to the mgr via bar.foo.com OR b) login separately to bar.foo.com before being able to see the unpublished Resources.

Do you mean to say the users you are creating cannot login to the manager? They immediately get "Access Denied"? If so, that is an issue with providing them access to the mgr Context, not any of the front-end Contexts.

No, they can access it, and they can create new resources. What they can't do is edit existing resources -- when one is clicked, the top logo and top nav areas show up normally, but everything below those (the left tree and the editing area) are replaced by "Error! Access denied."

There's nothing in the error log, btw. It seems like maybe it could be a server permissions issue and not a MODx thing? I'm really not sure.