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.

Installing SilverStripe

Getting SilverStripe up and running on your computer and on your web server.

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

temp folder


5 Posts   1647 Views


17 September 2010 at 8:33am Community Member, 32 Posts


I always did a temp-folder for silverstripe installations that I could delete the temp data on the server when needed (I needed it when I did changes of html SS code that it would change immediately in the browser with the deletion of temp files on the server).

For this I needed to put this code into an _ss_environment.php file which was in the root folder of all silverstripe installations.


define('TEMP_FOLDER', dirname(getcwd())."/tmp");


But this doesn't work anymore in the version 2.4.1.
Any advise how I could use that feature in newer versions?



17 September 2010 at 3:03pm Forum Moderator, 5511 Posts

AFAIK nothing should have changed in 2.4.1 that would have broken that. Do you just get it writing the cache to the incorrect folder?

Have you checked that SS is loading that environment file (i.e by putting a die() in it).


17 September 2010 at 11:44pm Community Member, 32 Posts

Hi Willr,

Thanks for your answer. It still doesn't work.

Asked differently: How can I achieve to have a temp directory of the 'viewed sites' where I can delete all the files if necessary on the server. I used to do that in earlier versions because only with this approach I could get rid of old *.ss html stuff when I changed html *.ss files. I experienced that *.ss files are not being updated straight away because there is a temp directory on the server. With the file in the first post I could bypass these files into a folder in my SS directory.
With 2.4.1 I just get a blank page and nothing is being dumped into the tmp directory.



18 September 2010 at 7:14am (Last edited: 18 September 2010 7:17am), Community Member, 18 Posts

It's easy to "build" a "own" silverstripe-cache:

- create a folder named "silverstripe-cache" in the root-directory of your silverstripe-installation.
- set the folder to chmod 0777 ( or eq. on Windows-os to read/write)
- start your /home with the parameter /?flush=1:

after this all temporary files would be build in this directory. If you have root-level-rights, you can delete the cache using a cronjob. But this is not the sense of caches bthw.

Attached Files

18 September 2010 at 10:37pm Community Member, 32 Posts

Thanks mate!

That was exactly what I was looking for!