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.

Archive /

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

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

SilverStripe Cache


Reply


5 Posts   3868 Views

Avatar
gakenny

Community Member, 153 Posts

11 September 2007 at 3:01pm

Hello,

Can I recommend that the SilverStripe Cache be located in a different path? By default, it is locates in the \tmp folder of the server. However, in a shared server environment, this location is used by multiple users and this can cause issues:
(1) The silverstripe-cache folder is created by user1 who has full permissions (and is the owner under PHPSuExec). user2 installs SilverStripe but cannot write to the silverstripe-cache folder because it was created and owned by user1.
(2) In a shared server environment, a user cannot browse to the \tmp folder to clean-up any files that may have been created by the user but the space is still allocated to them.

My suggestion that this folder is located under a specified folder under the root of the account.

Cheers,

Gary

Avatar
Andy

230 Posts

12 September 2007 at 10:04am

This was implemented a few weeks ago for the same reason you specified. SilverStripe still tries to using /tmp if it can first though.

Avatar
gakenny

Community Member, 153 Posts

12 September 2007 at 10:32pm

Hi Andy,

I downloaded the daily installation from CVS on Monday and I still had the same issue. Is there a possible problem with the test? ie. Write permissions to \tmp work but not to \tmp\silverstripe-cache.

Cheers,

Gary

Avatar
Andy

230 Posts

14 September 2007 at 10:10am

The latest daily build now always uses the local folder silverstripe-cache if present, so if permissions are not detected properly you can just create the silverstripe-cache folder.

Avatar
trogar1971

Community Member, 4 Posts

26 February 2008 at 1:50am

Suggestion:

If this is the case, then I'd suggest, that with new installs, you'd include this empty folder in the file structure. I am new to this framework/cms and having big issues trying to get it installed, and it was NOT part of the file structure as of 2-24-2008 when I downloaded this cool looking framework to see what it can do. Just a suggestion so that people don't have to go off hunting for where Silverstripe is tossing their cache files anymore, and don't have to dig through a forum to find out how to regulate where they are tossed.