We have done another install of 2.4 - In previous versions, the cache was written to the root tmp directory of the server, and that can be hungry on resources. So we used to create a directory within the client site root called silverstripe-cache and it used to write the files into client individual sites
To achieve that now (cache directory in the client root), the core has be changed as above, and we dont think that is a good thing. Willr, was there a particular reason to change that?
i just installed silverstripe with the cache folder within the project, cause my xp box chokes on the long paths it uses by default. it worked like it always did: i just created the silverstripe-cache folder in the silverstripe folder and it works without hacking the core. any other behavior would be a bug. what version of ss are you using? 2.4.0, 2.4 trunk?
is_dir() [function.is-dir]: open_basedir restriction in effect.
Means you cannot write the tmp files to /tmp/. To get around this issue create a 'silverstripe-cache' folder in your root folder and make sure the webserver has the correct permissions to read / write to the dir.