Thread

I am using engine hosting, and have MSM installed.  I have been developing multiple sites using a test domain call “nvadave.com”.  There are 5 sites that we are testing using subdomains like 96x.nvadave.com.  This has been working fine for quite some time.

Now I want to add a 2nd domain as follows:

- 96x.nvadave.com ==> /sites/96x (This is the one that has been working fine)
- 96x.fm ==> /sites/96x (This is the new one)

I called engine hosting and had them accept requests for the 96x.fm domain.  Now, I can go to the index page for my site from the new domain, but I cannot go anywhere else on my site.  I can’t get to scripts or styles or any of the directories under /sites/96x, they all kick me back to the home page.  I have setup a test subdomain in my DNS of http://new.96x.fm, which has an A record of 209.240.81.126.  If you go to the domain you will see the homepage of my site.  However, if you try to go anywhere else it kicks you back to the homepage.  The only reason the homepage renders is because all of the scripts, style and images are still coming from http://96x.nvadave.com.  If I try to go to the location of a script, style or image via the new.96x.fm domain, I cannot get to the files. 

Example:

http://96x.nvadave.com/sites/96x/styles/sidebar-summary.css  ==>  This works
http://new.96x.fm/sites/96x/styles/sidebar-summary.css ==>  This DOES NOT work…

Any help would be greatly appreciated…

Thanks,
Greg Weber

Greg, is sidebar-summary.css a stand alone .css file, or what exactly?

What is new.96x.fm? Compared to 96.fm?

Hi Sue,

It is a stand-alone css file, just an example of a file that should load source to the browser.  It doesn’t behave that way though, it simply goes back to the homepage.  But the homepage cannot load the scripts or styles.  I think it has to do with how engine hosting is accepting requests and how that is working with my .htaccess.

new.96x.fm is a subdomain of the domain we will eventually use for the site.  We just setup the subdomain to test the host settings.

EE renders the HTML, but the other scripts and styles are not available.  EE will not render any other pages in any other template groups, only the *index will render.

Thanks,

Greg

Is the new site inside or outside of MSM?

It’s inside of MSM, has been for months and has been responding to http://96x.nvadave.com with no problems.  Just wanted to have it respond to 96x.fm, as that is the real domain we want to use.

Greg

I understand you’re working with EngineHosting on getting this cleared up. Let me know when you’re ready to start troubleshooting the EE side of things.

The first thing I recommend is to have a directory off the root domain for stylesheets and JS files. I call mine /jscss - and all my .js and .css files live there. So when I put in my links for the .css files, I use the path to the main folder /jscss.

Thanks, Sue, I appreciate your help.  Yes, EH is working on it now, seems like a straight up Apache issue.  Do you know the EH people well?

I’ve worked with them off an on for the last 6 or 7 years.. so you might say that. 😊 We each have our own specialties, and I defer to their expertise.

How are things working now?

Is there a particular reason why you need to use new.96.fm instead of 96.fm?