Manual suggest to put ?flush=1 on the end of the URL for purging cache. When I do that I get install.php screen, and I have to delete cache manualy. Am I doing something wrong?
We've moved the forum!
Please use forum.silverstripe.org for any new questions
(announcement).
The forum archive will stick around, but will be read only.
You can also use our Slack channel
or StackOverflow to ask for help.
Check out our community overview for more options to contribute.
I'm not quite sure I understand you, Stevan. What is the URL that you're putting ?flush=1 on the end of? Is this after a successful installation?
?flush=1 clears out SilverStripe's own cache of compiled templates and file-manifest information. It doesn't clear the browser cache or anything.
My problem is that ?flush=1 does not delete CMS (those precompiled templates) cache... So i have problems when changing stuff... Maybe it is windows problem...
Is it enough to delete system temp directory to force CMS to recompile templates?
You have to put ?flush=1 on the URL that actually makes use of the template in question.
However, as you suggest, clearing out the temp folder will force SilverStripe to re-build everything.
On a hosting solution with limited access (basic FTP) I ran into trouble doing releases as the cache would kind of screw things up when new templates where released, especially in conjunction with included files, stylesheets etc.
The solution I found was to put a directory called 'silverstripe-cache' with write access from web server in the home directory where you'll also find 'mysite', 'sapphire' etc.
Silverstripe will create cache there, which you can then delete using a client such as lftp when doing a release.