Contexts as simple category containers

(2.2.5 /2.2.6) A Context Access ACL entry for anonymous users and Administrators is automatically created for new Contexts. Still neither usergroup can view resources in a non-web Context (404 error). I don't want to create resource groups or anything like that, just a plain ol' Context with free Resources.

Long ago I already gave up on trying to use multiple Contexts to organize resources for same domain. I only use them for Top Level Domains. But it would be nice to get it to work....I think I have tried every ACL variation my little brain can come up with, and have since dismissed the possibility of Permissions being the cause.

Can you test it on your system? Create a new Context and see if you can link to or view resources in it....?

Same here. It forwards me to the error page no matter what.

I also tried this:



But it doesn't appear to be parsed correctly.

One thing I didn't try was setting a placeholder for the ID of the other page and using this:

The URL is generated as expected. It's just that it won't go there.

I really think you should check .htaccess or index.php for redirects and domain routing.

I sounds like wrong redirection in my ears...

You are shure that you had switched the context forwarding in Core - Systemsettings to "yes"?

Hm. I've been doing this in a subdirectory installation on localhost. Maybe I'll try it again on the Cloud.

No, it won't work on the Cloud either. There has to be some way to access the pages from resources in other contexts! What are we missing?

There has to be some way to access the pages from resources in other contexts!

Yes, thats true.

I am on the cloud, default install... and after switching yesterday the Systemsetting "Context Forwarding"
to yes i could access IDs ouf other ressources out of the box without any Problems at all.

Maybe setup an empty development instance and verify... it works out of the box.

I had some issues in the past at the cloud, and support fixed that very very greatly on the fly...
did you ask them if this could be an Technical / Server issue?

In my case Gatewaymanager (which is used to route Domains to Contexts) fired that "oops, not found Page of modx" no 404... but a issue slightly in that direction you have actually.

Ah, missed that you use a localhost install too, sorry.

@theoretiker Could you test it out on the cloud or wherever :

On Same Domain
Different Context (web2)

Are you able to view resources in web2? And what are your settings

Thanks a lot

So this requires a gateway manager? The other contexts have to be treated as sub-directories? I have a multi-language site using subdirectories and a context switching plugin, but that's not what I mean here.