Hi there,

My image directory is being parsed by EE so I don’t see any images on my site and I can’t understand why!

My Setup
- I’m using Engine Hosting
- I’m using the Multiple Site Manager
- The problem is with my second site, which is a subdomain and is using a sub-directory within the main site’s structure
- EE pages are being displayed on the subdomain, but EE seems to be parsing all directories
- I’m using the ‘exclude’ method to remove index.php from my urls. This is working perfectly well on other servers with MSM and on the main site.

Here’s my code for the .htaccess file that’s in my sub-domain’s main directory:

Can anyone spot anything?

I’ve checked with the Knowledgebase on Engine Hosting, but guess what? The “How do I get support in the use of ExpressionEngine Core/Full?” is blank! Not very encouraging.

Cheers

Jim

I don’t think I entirely get what’s happening.  Can you link to it in action?  And you might want to remove the htaccess rewriting for testing purposes.  If it works with that gone and the index.php added back, we’ll know that’s part of the problem.

Hi Robin

Thanks for replying to my post. I’ve now removed the htaccess and I still can’t see any other directories.

For your information, I have an htaccess in my main directory as well, the contents of which are:

The bottom part is required by Engine Hosting for setting up a subdomain.
The directory name for my subdomain is ‘dev’. If I remove ‘dev’ from the main htaccess file I get an Error 500 on the subdomain.

I’ll PM you with a link.

Cheers

Jim

Hm- I can’t get to the subdomain at all- want’s authorization- returns HTTP/1.0 401 Unauthorized w/out it.  So- it’s locked down somehow.  But I don’t see it in the htaccess.  Huh.  I suppose you could have it required to access the template(s)?  In access restrictions?  Otherwise, got to be something going on server side.

Sorry - I’d forgotten that the template was locked down. It’s now accessible.

I’ve fixed it. It turns out that it was because I was using the ‘exclude’ method to remove index.php from the urls. Using the ‘include’ method instead solved the problem.

The Engine Hosting documentation states the following about this:

Anything I should know about removing index.php from my URLs on EngineHosting’s servers?

Removing index.php completely from ExpressionEngine’s URL structure is a community supported feature rather than an official feature.  With that in mind there is a notice added by hosting staff addressing the use of the “Exclude Method” only, which you can find full information here:  Remove index.php from URLs

The problem is that in the EE docs it doesn’t say anything about Engine Hosting at all! It’d be great if the folks at Engine Hosting could work a little on their documentation. Earlier this week I had to tell them that their “How do I get support in the use of ExpressionEngine Core/Full?” page was blank! It has since been populated.