I get the infamous 500 Internal Server Error after upgrading to 6.20 from 6.19.
When I rename htaccess, I get the offline page.
I cannot figure out what is wrong with htaccess. Maybe it comes from something else but I don't know what is wrong.
Here is my htaccess.:
#
# Apache/PHP/Drupal settings:
#

# Protect files and directories from prying eyes. Order allow,deny

# Don't show directory listings for URLs which map to a directory.
Options -Indexes

# Follow symbolic links in this directory.
Options +FollowSymLinks

# Make Drupal handle any 404 errors.
ErrorDocument 404 /index.php

# Force simple error message for requests for non-existent favicon.ico.

# There is no end quote below, for compatibility with Apache 1.3.
ErrorDocument 404 "The requested file favicon.ico was not found.

# Set the default handler.
DirectoryIndex index.php

# Override PHP settings. More in sites/default/settings.php
# but the following cannot be changed at runtime.

# PHP 4, Apache 1.

php_value magic_quotes_gpc 0
php_value register_globals 0
php_value session.auto_start 0
php_value mbstring.http_input pass
php_value mbstring.http_output pass
php_value mbstring.encoding_translation 0

# PHP 4, Apache 2.
php_value magic_quotes_gpc 0
php_value register_globals 0
php_value session.auto_start 0
php_value mbstring.http_input pass
php_value mbstring.http_output pass
php_value mbstring.encoding_translation 0

# PHP 5, Apache 1 and 2.

php_value magic_quotes_gpc 0
php_value register_globals 0
php_value session.auto_start 0
php_value mbstring.http_input pass
php_value mbstring.http_output pass
php_value mbstring.encoding_translation 0

# Requires mod_expires to be enabled.

# Enable expirations.
ExpiresActive On

# Cache all files for 2 weeks after access (A). ExpiresDefault A1209600


# Do not allow PHP scripts to be cached unless they explicitly send cache
# headers themselves. Otherwise all scripts would have to overwrite the
# headers set by mod_expires if they want another caching behavior. This may
# fail if an error occurs early in the bootstrap process, and it may cause
# problems if a non-Drupal PHP file is installed in a subdirectory.
ExpiresActive Off

# Various rewrite rules.

RewriteEngine on

# If your site can be accessed both with and without the 'www.' prefix, you
# can use one of the following settings to redirect users to your preferred
# URL, either WITH or WITHOUT the 'www.' prefix. Choose ONLY one option:
# # To redirect all users to access the site WITH the 'www.' prefix,
# (http://example.com/... will be redirected to http://www.example.com/...)
# adapt and uncomment the following:
RewriteCond %{HTTP_HOST} ^mysite\.fr$ [NC]
RewriteRule ^(.*)$ mysite/$1 [L,R=301]

#
# To redirect all users to access the site WITHOUT the 'www.' prefix,
# (http://www.example.com/... will be redirected to http://example.com/...)
# uncomment and adapt the following:
# RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC]
# RewriteRule ^(.*)$ http://example.com/$1 [L,R=301]

# Modify the RewriteBase if you are using Drupal in a subdirectory or in a
# VirtualDocumentRoot and the rewrite rules are not working properly.
# For example if your site is at http://example.com/drupal uncomment and
# modify the following line:
# RewriteBase /drupal
#
# If your site is running in a VirtualDocumentRoot at http://example.com/,
# uncomment the following line:
RewriteBase /

# Rewrite URLs of the form 'x' to the form 'index.php?q=x'.
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !=/favicon.ico
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]

# $Id: .htaccess,v 1.90.2.5 2010/02/02 07:25:22 dries Exp $

Comments

napounet’s picture

Nevermind. It is fixed. Not sure what was wrong but I used the htaccess from 6.20 with some changes and it worked.

redrider’s picture

well, what kind of changes did you make to your .htaccess?

I ahve the same problem right now

noxprime’s picture

I also have the same problem, help please !

edit : i found a solution, the problem is clean urls. Deseable it by using link "yoursite/?q=admin/settings/clean-urls"

napounet’s picture

I tried to check clean urls by adding /?q=admin/settings/clean-urls as suggested and it worked partially.
By partially, it means that I can disable clean URLs and get my site back but it is generating lots of errors since lots of urls were based on clea urls.
It needs more work to get things the way they were.

jdg100’s picture

I have the same problem - could you please post your new (good) .htaccess file too?

Thank you

peezy’s picture

You can do this without anyone else's .htaccess file. Simply replace your new .htaccess file (6.20) with the .htaccess from your old (6.19) site. This assumes you made a back-up, which you should always do before upgrading.

TimAlsop’s picture

I also started getting this issue after upgrading to 6.20.
I compared the .htaccess from 6.19 and it is same as from 6.20. It seems this file was not changed when Drupal 6.20 was released.

I have turned off Clean Urls, but I prefer not to have to do this. Is there a better solution ? Somebody mentioned they changed .htaccess to fix the issue, but they didn't say what they changed ??

peezy’s picture

Try this:
1. open your .htaccess file
2. Find the part that says

# If your site is running in a VirtualDocumentRoot at http://example.com/, 
# uncomment the following line:
#RewriteBase /

3. Change the line that says #RewriteBase / to RewriteBase /
4. Save the file, flush your cache , and try the clean URL test again.