[wp-testers] rewrite issues with 1&1 hosting.

[Chris]

I think the cPanel upgrade may have caused this problem. The change to 
the .htaccess file is obscure and would seem to be produced by some 
automated process. We had one of our Hostgator account's .htaccess files 
mangled in the same fashion very early this morning.

I'm tempted to write-protect the file so that it cannot be mangled by 
any future automated processes, but I'm quite certain that the process 
that does this has greater privileges than I do and would just mangle 
the file anyways.

So for anyone getting mysterious 500 errors on your hosted WordPress 
sites today, check that .htaccess file and make sure that it hasn't been 
changed.

- Chris Jean

Will Garcia wrote:
>  I think the line
>
> RewriteRule . Arrayindex.php [L]
>
> caused the error and should be changed to
>
> RewriteRule . /index.php [L]
>
> Just thinking out loud.
>
> On Tue, Nov 4, 2008 at 11:56 PM, Krusty Ruffle <
> krustyruffle at rustykruffle.com> wrote:
>
>   
>> As soon as I enabled Permalinks I lost all css on the admin panels, and the
>> public pages gave 500 internal server errors.
>>
>> Changing this:
>>
>> # BEGIN WordPress
>> <IfModule mod_rewrite.c>
>> RewriteEngine On
>> RewriteBase Array
>> RewriteCond %{REQUEST_FILENAME} !-f
>> RewriteCond %{REQUEST_FILENAME} !-d
>> RewriteRule . Arrayindex.php [L]
>> </IfModule>
>>
>> # END WordPress
>>
>> To this:
>>
>> # BEGIN WordPress
>> <IfModule mod_rewrite.c>
>> RewriteCond %{REQUEST_FILENAME} !-f
>> RewriteCond %{REQUEST_FILENAME} !-d
>> RewriteRule . /index.php [L]
>> </IfModule>
>>
>> # END WordPress
>>
>> Fixed it right up... ( I copied that from a version 2.6.3 .htaccess file.)
>> Unfortunately, this is on a shared hosting plan so I have no access to
>> apache's error logs...
>>
>> Just thought somebody might like to know :)
>> _______________________________________________
>> wp-testers mailing list
>> wp-testers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-testers
>>
>>     
>
>
>
>