rewrite to htaccess file shut down site
-
Hi,
I think this plugin just rewrote a bit of incomplete code to my .htaccess file which resulted in the site being unavailable (500 error). Luckily our server support team found it, removed it, and all was OK again.
However i thought others might have the same issue, or that it may be a development issue for this plugin, so thought I’d share the details…
at the bottom of the compromised .htaccess file it had this code:
# BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress ewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress
where you can see the extra, incompletely written rewrite rules repeated, and in the restored/corrected .htaccess file it looks like this:
# BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress
which is normal.
Also this is not the first time that our site has crashed and it ended up being an issue with extra erroneous info being added to the .htaccess file – though I understand that some other plugins write to this file too, so it’s hard to pin down where the glitch is!
I’d be interested to hear of anyone else that’s had this problem – or if there’s a setting that I’ve done that could have causesd it?
Cheers.
- The topic ‘rewrite to htaccess file shut down site’ is closed to new replies.