-
- 932 Posts
-
- 932 Posts
Good stuff, thanks for reporting back.
Setting up multiple contexts can sometimes be a pain! Glad you got it sorted though
There's an additional challenge: my content editors cannot save newly created resources. They get the infamous 'access denied' error message when saving a new resource. It happens in all contexts, including 'web'.
Working on existing resources is fine. compress_js and compress_css are off.
The admin can save newly created resources.
Maybe this has nothing to do with contexts, but it happens right after creating the extra contexts. But then again: the content editors did not create new resources for the existing 'web' context, just editing.
(Yes, they have access to the contexts: they see the trees and can open resources.)
[ed. note: handjes last edited this post 5 years, 11 months ago.]
-
- 932 Posts
check their access policy sounds like they may not have the correct permissions (you could swap it for a different policy to quickly check if this is the issue). Also check that that new resources created they have access to in the resource group.
It has the correct permissions. I have been working with these permissions on many sites. Permissions include the often mentioned class_map, view_template, view_user, etc.
I tracked the error down to a subdocument in connectors/index.php:
{"success":false,"message":"Toegang geweigerd!","total":0,"data":[],"object":[]}
I really don't understand why this suddenly is happening. (I did not update anything)
Strangely, a customer just called to mention they have the same issue on a MODX site without extra contexts! What is going on?
You won't believe this: the permission 'new_document_in_root' was unchecked on both sites! Why did this happen?
I'm going to check all my sites now.