Warning: I am able to write to the configuration file:

Hey everyone,

I've been going through various threads regarding this topic, and I'm having an issue with this error message.

I got the infamous "red box" on my website (chmod 644). I sent an email to my hosting support to help me out with this (since I'm a virgin with hsphere), and they replied that this error had been fixed and so on.

I don't have any problems logging into my admin, but when I click on the "online catalogue" button (top right corner), I get this "HTTP 500 Internal Server Error".

I need to get this rectified ASAP, and my hosting support, well.... let's not go there.

Can anyone help me with this? What files and where would they be located in hsphere that I need to change?

Working 16 hour days is taking its toll, so please break it down for me.

Much appreciated :)

Dave

Whats d site address?

It's www.indigodecorative.com

I recently had another issue where the site doesn't even show up.

My web support mentioned that I have to restore files from the latest backup. This is getting more confusing as each day passes.

no error just a white page

make sure you have only one index.php no other index page with it

As the problem seems to have been created by your Hoster, they would be the ones best able to correct.

If changing permissions creates a problem then use this other method; to remove the Big Red Error msg.

around line 24 of /includes/init_includes/init_header.php
define('WARN_CONFIG_WRITEABLE', 'true'); << change to false

Only do the above if you "know" the "configure.php" is set to 644.

Should have said:

Only do the above if you "know" the "configure.php" is set to 444.

you need to chmod 444 that config file.

If you don't have shell access, you probably have some kind of file management tool in your hosting control panel.

if you are using dreamweaver or any other file management program just right click on the file on the remote server and click manage or edit permissions.

Hey everyone,

Thanks for the responses. There were other site issues that I was faced with after my original post, and after restoring a database, things seemed to be working smoother for some reason, and I'm not complaining lol.

It seems okay now, thank you once again.

Dave :smile: