Access denied while editing resources on multiple context setup

Sorry, you're right. I'm not used to looking at them with all the permissions exposed.

See if changing the policy to Administrator solves the problem.



------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Done...and no luck. I tried switching it separately and at the same time in mgr and the problem context, but no luck.

Bob, don't feel obligated -- this would definitely be above and beyond -- but would you be interested in looking around for yourself? I think I can trust you with a temp admin login ;-) I'm just really trying to figure out if this is just something silly I did, or an actual bug that needs to be reported.

I can take a look, though it's starting to sound like a bug. You can email me the credentials here: http://bobsguides.com/contact-form.html (I'll need to be a Super User to see everything).


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Thanks so much. Just sent the credentials your way. You're a sudo user, so you should have full access. Please let me know when you're done and I'll remove the user.

I don't see anything obvious, but there are a few things you could try:

1. Change the aliases on the non-web context docs so that you don't have any resources on the site with duplicate pagetitle/alias combinations (e.g., JillsHome)

2. Don't give any resources the alias of "index"

3. Remove the two Member Context Access ACL entries (they really shouldn't have a policy of Resource since that's not a Context Access style policy -- it's a Resource Group Access Policy).

4. Turn off the compress_js and compress_css System Settings (if you haven't already).

TBH, I don't think any of that should really matter, but we're running out of options.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Thanks, but no dice. I did all four, but still get the same error. Bug report time, you think?

I would say so. I would report it with the sub-context policy set to Administrator.

I should mention that it's possible that you have a corrupted file in the install, especially if you used FTP to transfer the files.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Done! Thanks again for the troubleshooting help: http://tracker.modx.com/issues/7925

I was able to replicate this in MODX 2.1.1, so it's not a corrupted file. BTW, creating a Context Access ACL entry for the web context for the user group solves the problem (though it shouldn't matter). As a workaround, you could do that and hide the web resources with resource groups.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html