-
☆ A M B ☆
- 872 Posts
Hello,
I encountered an odd issue on a website using two context.
Whenever i clear cache (directly or by saving a snippet,plugin, etc...) modx logs that it could not load my specific context (web and mgr are still accessible).
What’s odd is that the configuration is an exact copy of another one which work like it should.
What i saw in the core/cache/mycontext directory is that the file "context.cache.php" is erased on clear cache and regenerated when a page is refreshed in the desired context.
This file is not created upon refresh which cause a 404 error.
The only way to recreate the file is to save whatever resource from the specified context so that it can be generated again.
Any hint what could cause this issue ?
-
☆ A M B ☆
- 872 Posts
What’s even more bizarre is that it loads the specific context error page the right way.
-
☆ A M B ☆
- 872 Posts
Testing again!
In fact, i don’t even have to save the resource to regenerate the context.cache.php files, i just have to access a resource (not even on the specific context).
On the first test site, when i refresh the page on the front end, the context.cache.php is regenerated automatically.
-
☆ A M B ☆
- 872 Posts
Unfortunately it didn’t work.
-
MODX Staff
- 10,725 Posts
How are you initializing or switching to the proper context?
-
☆ A M B ☆
- 872 Posts
Yes, i’m using a plugin onHandleRequest (and have tested by putting a switch directly in the index file as well).
Plus, it works since when i click on a resource in the manager, i can re-access the pages on the Front End.
-
☆ A M B ☆
- 872 Posts
I gave the anonymous an access with load only and Administrator as Super User.
I didn’t implement resources group yet.
-
☆ A M B ☆
- 872 Posts
I did some additional test (with both MODx 2.0.4 and 2.0.5) the context send me to 404 page only in FF.
In either IE,Opera or Chrome, the context.cache.php file is regenerated properly when i refresh the page on clear cache.
From here on, i don’t know if the problem comes from FF or MODx...
