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've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Installing SilverStripe /

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

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

[SOLVED]Heavy running Error: two ss websites don't works contemporanery


Go to End


2 Posts   1264 Views

Avatar
biapar

Forum Moderator, 435 Posts

10 December 2010 at 1:24pm

Edited: 10/12/2010 1:29pm

Hi,

I've ported two ss websites from Linux to new Win2k8 r2 webserver.
Sites run ok, but not if are on togheter, because there is an erron on ss cache, that is one site overwrites silverstripe temp file that are under c:\windows\temp.
Sites are 2.3.2 and 2.3.3 version.
I think that problem is that ss versions not write a cache directory ( under c:\windows\temp ) for each site. Is it?
My web config

<system.webServer>
<directoryBrowse enabled="false" />
<rewrite>
<rules>
<clear />
<rule name="SilverStripe Clean URLs" stopProcessing="true">
<match url="^(.*)$" />
<conditions logicalGrouping="MatchAll" trackAllCaptures="false">
<add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
</conditions>
<action type="Rewrite" url="sapphire/main.php?url={R:1}" appendQueryString="true" />
</rule>
</rules>
</rewrite>
<defaultDocument>
<files>
<clear />
<add value="Default.htm" />
<add value="Default.asp" />
<add value="index.htm" />
<add value="Default.aspx" />
<add value="index.php" />
</files>
</defaultDocument>
</system.webServer>

Why?

Avatar
biapar

Forum Moderator, 435 Posts

10 December 2010 at 9:58pm

The problem was, as I think, silverstripe-cache dir.

Under windows server, by default, this dir is under c:\windows\temp and old Silverstripe versions ( 2.3.x ) use this dir.
Then if you have more site, all site write cache files into this dir and so use the same manifest files.

WorkAround is to create a silverstripe-cache into web site dir.

This problem don't exist for version 2.4 because under c:\windows\temp, there is a silverstripe-cache dir for each site.

Bye