Thread

Here’s the fix for DH.
AddHandler application/x-httpd-php .php

Here’s a sample of a working HTACCESS file that lives on a site on DH (I have lots. this works)

AddHandler application/x-httpd-php .php
ErrorDocument 404 /missing.html

#EE index.php replacement file and folder method
RewriteEngine On 
RewriteCond $1 !\.(gif|jpe?g|png)$ [NC]
RewriteCond %{REQUEST_FILENAME} !-f 
RewriteCond %{REQUEST_FILENAME} !-d 
RewriteRule ^(.*)$ /index.php/$1 [L]

php_value memory_limit 64M     
php_value upload_max_filesize 100M 
php_value post_max_size 100M

Here’s the fix for DH.
AddHandler application/x-httpd-php .php

FYI…

Adding the above line to my htaccess solved the original problem I was having on Dreamhost. BUT - just yesterday this line was the cause of another problem - I wasn’t able to Save Templates as File or Upload Images via the Publish Tab. Removing that line solved the issue.

Here’s the thread about that…
http://ellislab.com/forums/viewthread/106046/#533541

Anyone know why that line would cause that? Does that line have to be above the rewrite rule to remove index.php?

Chris,

Thanks for the code, but it didn’t help. It just made the entire site unavailable. I had actually tried the Addhandler code before seeing your response and got the same result with the file and directory check method. I even tried to just replace index.php with something else (the approved method) and it wouldn’t work.

I’ve opted to just put the index.php back in, and open an EngineHosting account in preparation for a future move to a company with intimate knowledge of EE. There may be something minor that I’m not doing, but Dreamhost has informed me that they won’t help with this issue, although they did say that my account shifted from Apache 2.0 to 2.2 during the move.

Thanks,
Sean

One thing I’d suggest, regardless of your host, is to install the Deeploy helper module

You’ll quickly see where all of your paths are going. With DH, you should always remove the .name from your directory path “/home/.baba/” or whatever… because sometimes they change the physical location of your stuff, and that .name is the name of that machine… thus hosing your site if you’ve used that path anywhere.

I’ll look into any additional settings I have for my DH setups. I’ve had a few recent blank pages when they upgraded apache, but I managed to fix them all with either removing the .name and/or setting the HTACCESS file.

You might also want to try using the whole thing:

AddType application/x-httpd-php .php
Action application/x-httpd-php /cgi-bin/php.cgi

I had some problems like this on DH (http://ellislab.com/forums/viewthread/100397/).

My eventual solution was to remove any hacks I had for the index.php and get my site all working again. Then I used LG’s .htaccess Generator and removed the {ee:pages} tag (noted in the thread I referenced). Then everything was working fine again.

This happened when I was moved servers, just like you.

Thanks, Erin. That worked. I had to manually add “tags” to the htaccess generator code so the tag module could work, but that was the only minor bump.

Chris, Thanks for the deploy helper suggestion. It wasn’t useful in this situation, but looks like it will be in many others. Also, thanks for the multiple code suggestions.

Sean

Glad I could help.

One thing I’d suggest, regardless of your host, is to install the Deeploy helper module

Hmm…I haven’t come across that before.  Looks very useful!  Thanks for the link, Chris.

I had a problem with my DH setups this past week as well.  It wasn’t related to this particular problem but the response from DH as the same (“bosses messed with the config files”).  They fixed it ASAP, but I wonder why people who apparently don’t know what they’re doing are messing with the server config files.

They might know what they’re doing, and still cause problems. Server maintenance is a PITA.