ENVIRONMENT_CACHE issue/error?
Permalink
Hi all, got a strange one for you all today....
One of my clients has moved their site into a development area for me to have a play with but I'm getting the loved white screen error.
I've been trying to resolve for a while now and done all the common things.
I can't access any page (this includes index.php/dashboard, index.php/login etc)
I moved the site into a local environment with PHP warnings turned on and got an error saying that C5 was trying to include files from "/Users/<username>/Dropbox/Clients/../././" etc, a local resource on my clients own machine.
I searched the whole site for the string and found it in the Config table under ENVIRONMENT_CACHE.
On a seperate install, I deleted the value and it loaded the site, but no content/theme loaded etc.
So, my question is, how do we refresh/update this value without breaking the site and having no access to the dashboard.
5.6.0.2 by the way if anyone requires that. The core folder /concrete is 5.6.0.2 - no /updates overrides.
Any ideas welcome.
Job.
One of my clients has moved their site into a development area for me to have a play with but I'm getting the loved white screen error.
I've been trying to resolve for a while now and done all the common things.
I can't access any page (this includes index.php/dashboard, index.php/login etc)
I moved the site into a local environment with PHP warnings turned on and got an error saying that C5 was trying to include files from "/Users/<username>/Dropbox/Clients/../././" etc, a local resource on my clients own machine.
I searched the whole site for the string and found it in the Config table under ENVIRONMENT_CACHE.
On a seperate install, I deleted the value and it loaded the site, but no content/theme loaded etc.
So, my question is, how do we refresh/update this value without breaking the site and having no access to the dashboard.
5.6.0.2 by the way if anyone requires that. The core folder /concrete is 5.6.0.2 - no /updates overrides.
Any ideas welcome.
Job.
I'm not convinced it's an optional functionality. As I understand it in 5.6 onwards site settings are cached and that's what's causing the issue and that cannot be turned off.
It makes sense really. You install the site in a local area, develop it and in the mean time all the environment settings will have been cached. But when you move the site it'll still be looking at the cache rather than an updated set of configuration values.
Just need to find out how to update the cache ..
It makes sense really. You install the site in a local area, develop it and in the mean time all the environment settings will have been cached. But when you move the site it'll still be looking at the cache rather than an updated set of configuration values.
Just need to find out how to update the cache ..
I expect once you know what is happening, the solution will be to put their site in maintenance mode, switch off whatever it is, take a new clone, then re-eneable their site. On the basis that its always easier to have a clone that works, rather than trying to patch up a clone that does not.