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.

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

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

multisites possible?


Reply


107 Posts   19159 Views

Avatar
FullWebService

Community Member, 38 Posts

6 October 2010 at 6:58am

Can't seem to get it to work either. Did all the steps, but now it just loads for a long time and then I get a blank page.

I've got a execution time error twice, when the loading took more than 30 seconds. Once on line 289 in /sapphire/core/ManifestBuilder.php and once in line 336. Both lines do a scandir, so there's something wrong there... can't for the life of me figure out what.

Avatar
honeybunny

Community Member, 79 Posts

6 October 2010 at 7:49am

@FullWebService,
Is it referencing a specific file or directory? Presumably it is either finding something that it doesn't know what to do with or it is not finding something it needs. Also, is it giving the error when you install the cms on the primary domain or the sub-domain? (Difference being that if it's working on one then it's probably just a keystroke or naming error for the second install.)

Keep the faith, even with my limited php I found this substantially easier to get up and running than the sub-sites module.

HB

Avatar
FullWebService

Community Member, 38 Posts

6 October 2010 at 8:12am

Edited: 06/10/2010 8:48am

Can't find anything specific. Doesn't even write an error to the log if the execution time stays under 30 seconds. Both the lines in ManifestBuilder it sometimes times out on there's a scandir of $folder.

I've put an echo $folder on line 289 and get this:

/var/www/vhosts/sitename.com/httpdocs/cms
/var/www/vhosts/sitename.com/httpdocs/cms/cms
/var/www/vhosts/sitename.com/httpdocs/cms/cms/cms
/var/www/vhosts/sitename.com/httpdocs/cms/cms/cms/cms

Until there's 20 times /cms. Then it actually goes through the folders:

/var/www/vhosts/sitename.com/httpdocs/20 times /cms/code
/var/www/vhosts/sitename.com/httpdocs/20 times /cms/code/reports
/var/www/vhosts/sitename.com/httpdocs/20 times /cms/code/sitefeatures
/var/www/vhosts/sitename.com/httpdocs/20 times /cms/code/staticpublisher
/var/www/vhosts/sitename.com/httpdocs/20 times /cms/css

etc...

Then it goes through the same folders with 19 times /cms, then 18 times, then 17 times... etc.

Really weird.

Normal installs are no problem, btw. Made dozens. That's why I want this so much :-)

Avatar
honeybunny

Community Member, 79 Posts

6 October 2010 at 1:42pm

Most of this is way above my pay grade so I won't be offended if someone steps in and says I'm going down a completely wrong path.

My first question is whether anything is working? Are you trying to get a previously working (primary) domain up after making the changes to accommodate multisites or is the problem with the subsite? Or are you working from a fresh install?

At first glance it seems to me that manifestbuilder.php is the file that brings in all the other pieces of SS, and if it is kicking back on cms then it's telling you that it can't load it. I would look at that folder, if you're working from a fresh install, it's possible that the permissions were changed or the file itself was somehow corrupted during the upload or unpacking process. It should only take a minute to reload it and try again.

Since you say that you haven't had any problem installing SS before, my second step would be to re-check what you did to go from a working version to watching scandir across your screen. Banal's instructions were fabulous and invaluable, but when I was researching a solution for my problem I found that everybody seemed to have to do things slightly differently to get things to work. Some people had to change permissions, alter the htaccess or add a cache folder, others didn't. I can't imagine how anything in the instructions would leave you unable to load, but who knows.

Sorry I can't be more helpful, but my errors were related to permissions, file location and a misinterpretation of the code for the symlink. All things that are relatively easy to trace and well within my scope...

HB

Avatar
FullWebService

Community Member, 38 Posts

6 October 2010 at 8:41pm

I think it has to do with the way I make symlinks. Can someone post an example how they did this?

TIA

Avatar
banal

Community Member, 901 Posts

6 October 2010 at 8:46pm

Edited: 06/10/2010 8:46pm

I create symlinks to folders using the following command:

ln -s /path/to/source/folder /path/to/target/folder

Avatar
FullWebService

Community Member, 38 Posts

6 October 2010 at 9:06pm

Ah, I did it the same way... so that's not it.

Thanks for the reply!

Avatar
FullWebService

Community Member, 38 Posts

6 October 2010 at 9:22pm

Now I have a bunch of symlinks that I made while testing that are conflicting with the "right" symlinks. Can't seem to remove them... This is really going from bad to worse.