• ncounter this error today when accessing my blog at work. So I contacted my host HelpDesk. They say, that the error my due to a Interference with an .htaccess file and suggested few things. Rename or delete the file so below is the actual file I have renamed.

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress
     !=POST
    RewriteCond %{QUERY_STRING} !.*=.*
    RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$
    RewriteCond %{HTTP:Accept-Encoding} gzip
    RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html.gz -f
    RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html.gz [L]
    
    RewriteCond %{REQUEST_URI} !^.*[^/]$
    RewriteCond %{REQUEST_URI} !^.*//.*$
    RewriteCond %{REQUEST_METHOD} !=POST
    RewriteCond %{QUERY_STRING} !.*=.*
    RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$
    RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html -f
    RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html [L]
    </IfModule>
    
    # END WPSuperCache
    
    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress

    So my intuition said, rather than rename it fixed it, that’s my problem. I researched it and the recommendation is to delete previous plug-in. In my case, its WPSuperCache that I had installed lately.

    Since I not that familiar with this. I would like to seek assistance on this one.

Viewing 1 replies (of 1 total)
  • Did the problem go away once you renamed the .htaccess (which disables it)?

    Your .htaccess looks like a mess with duplicated rewrite stuff, so starting over with a new one seems like a good idea. A new .htaccess should be generated if you save your custom permalinks settings in the dashboard and a file named .htaccess does not already exist.

Viewing 1 replies (of 1 total)
  • The topic ‘Internal Server Error w/ httaccess’ is closed to new replies.