30 July 2012 at 9:52pm
I've recently started a site in SS2.4.7 using the subsites module, works fine on my localhost however trying to get it to work on my Mediatemple Grid Service is proving difficult. I can set up subdomains on my server which creates a folder for me automatically, however I am informed by mediatemple that they need an index.htm in there for it to work. I'm a bit hazey on how all this stuff works anyway, my knowledge on the subject is only basic. I'm assuming there is something I can do with .htaccess to define other urls but there also must be a setting on the server which is overiding everything which is why my subdomains get a 403 Forbidden.
Has anyone else had any experience of using subdomains in Silverstripe?
1 August 2012 at 9:47pm
An update to what I've written already.
I contacted Mediatemple who said that the server is not configured for what I am describing. Their advice was to create a folder with the subdomain name, a folder inside there named "html" and inside that an index.htm or index.php file. This does work for individual files I want to upload but of course the result I want is for Silverstripe to dynamically take care of this for me.
The thing is I'm not that savy with knowledge of servers. What should I be asking them to make them understand how the subsites module in Silverstripe works? Is it something as simple as utilising the htaccess file?
I see you contacted (mt) Media Temple customer support already and they were able to help you out a little bit with your issue. I wish I can answer your specific issue for you and get it fixed but unfortunately we are not trained in SilverStripe. However, I have done a bit of research and found a previous forum post with what looks like a similar issue. The person who posted it was on a (dv) Dedicated-Virtual Server. I am including the link below.
8 August 2012 at 2:41am
I think the issue could have been that I had set up subdomains on the server when testing the server prior to trying with silverstripe. The Silverstripe method works fine I think, perhaps the issue was that it was just playing catch up which is why even after deleting dns zones on the server the sites still gave me a 403 error. Persist with time and these things sometimes sort themselves out.
Thanks for the reply though Drew and thanks to mediatemple for the speedy responses and their support.