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.


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

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

Cache and SilverStripe 2.2.0-rc3


5 Posts   2221 Views


24 November 2007 at 4:40pm Community Member, 153 Posts


With this new version, have you relocated the cache folder back to the /tmp directory on the server?

Previously, I have created a folder called silverstripe-cache in the root of the site and SilverStripe happily used this. Can this be reinstated?




25 November 2007 at 11:30am 121 Posts

This got me too. It seems that the ordering has been changed so that it:

1) Looks for a folder called silverstripe-cache-path-to-web-root in the web root

2) Looks for a folder called silverstripe-cache-path-to-web-root in the system tmp folder and if it's not there then it tries to create it

3) Falls back to a folder called silverstripe-cache in the web root if 2) fails (which is unlikely)

Whilst I can see the point of having a site unique cache directory if you create it in the system tmp directory, I can't see why it needs to include the path in the folder name in 1) - seems kind of redundant.


26 November 2007 at 11:48am Community Member, 153 Posts

Thanks jam13 - this changed from RC1 to RC3!

How did you find this one out? Did you look at the code or was it documented somewhere that I missed?


27 November 2007 at 11:29pm 121 Posts

Noticed the files in /tmp and then looked in the code. It's in Core.php IIRC.

RC4 has been changed so that "silverstripe-cache" in the web root works again.


27 November 2007 at 11:39pm (Last edited: 27 November 2007 11:49pm), Community Member, 5 Posts

Creating a silverstripe-cache subfolder in the main Sstripe folder is working
and there is no more /tmp/silverstripe-cache-something folder. I think this
subfolder should be already created in the default install SStripe package with
acces rights verification like some other folders.

EDITED : and a .htaccess to forbid direct web acess of files in that folder :)