By thebeacon on

Not sure what I did other than replacing "advanced contact" module folder from a back up on the computer. Now When ever I log in to admin Drupal login I get blank pages on FireFox and 500 Internal Server error message on internet explorer. In order to see my site again I have clear all the cash and cookies in the browser. basically I cannot log in anymore in to admin account. I have not created any recent backups. What are my options? Thank you!

⋅ Categories: Drupal 5.x

Comments

thebeacon’s picture

thebeacon commented

Is there are way to somehow reset some setting in order to be able to log in to admin account?

jvinci’s picture

jvinci commented

I'm getting the same error and I haven't changed a thing.

I posted the symptoms in a reply to thebeacon's other post at: http://drupal.org/node/207810

jvinci’s picture

jvinci commented

OK, I think I figured out the problem.

Here's a few lines of code from my .htaccess file:

# PHP 4, Apache 1.
<IfModule mod_php4.c>
# For security reasons, mod_php is not used on this server. Use a php.ini file for php directives
#   php_value magic_quotes_gpc                0
# For security reasons, mod_php is not used on this server. Use a php.ini file for php directives
#   php_value register_globals                0
# For security reasons, mod_php is not used on this server. Use a php.ini file for php directives
#   php_value session.auto_start              0
# For security reasons, mod_php is not used on this server. Use a php.ini file for php directives
#   php_value mbstring.http_input             pass# For security reasons, mod_php is not used on this server. Use a php.ini file for php directives
#   php_value mbstring.http_output            pass
# For security reasons, mod_php is not used on this server. Use a php.ini file for php directives
#   php_value mbstring.encoding_translation   0
</IfModule>

BlueHost had just upgraded Apache and PHP on my server. The server must have had a setting that turned off "mod_php". Then, when I updated my .htaccess file, it must have commented out all of the code in my .htaccess file. (I don't know why I didn't see it before.

Anyway, I replaced the .htaccess file (perhaps BlueHost has since turned "mod_php") and my site is back up and running.

-JV