Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

Archive /

Our old forums are still available as a read-only archive.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo

Purging cache

Go to End

5 Posts   9259 Views


Community Member, 3 Posts

20 October 2006 at 8:51am

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?


Administrator, 690 Posts

20 October 2006 at 10:07am

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.


Community Member, 20 Posts

20 October 2006 at 8:24pm

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?


Administrator, 690 Posts

24 October 2006 at 10:47am

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.


Community Member, 7 Posts

15 October 2008 at 7:05pm

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.