Quizzey

I'm having a problem getting into both the site and administration. When I went to bed everything was ok but this morning I'm getting these messages.

When I try to visit the site I get the message

This site is temporarily unavailable.
Please notify the System Administrator

Whe I try to login to administrator I am unable to do so and I get this message

Warning: database(configuration.php): failed to open stream: No such file or directory in /home/xxxxxx/public_html/classes/database.php on line 68

Warning: database(): Failed opening 'configuration.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/xxxxxxx/public_html/classes/database.php on line 68

Warning: database(offline.php): failed to open stream: No such file or directory in /home/xxxxxxx/public_html/classes/database.php on line 69

Warning: database(): Failed opening 'offline.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/xxxxxxx/public_html/classes/database.php on line 69


Any help would be appreciated?

Tom

Gayle

__________________
"Unix gives you just enough rope to hang yourself -- and then a couple of more feet, just to be sure" --- Eric Allman

Quizzey

Thanks for that Gayle. When I run it I get this error

MySQL login Failed Access was refused.
Check your database username/password in configuration.php.
Check that the user exists on your MySQL database and has the correct password.Check that the hostname is correct and not being blocked by a firewall.

MySQL database selection Failed

Then I had a look at the database tru cpanel and the user name is still there but I have no idea how to check what the password is. I also had a look at the database tru phpMyAdmin and all the tables are there.

How would I check the password for the usere in the database.

Tom

Trevor

Hi:

I had a similar problem. The only thing that successfully worked for me for an upgrade from 1.0.5 or 1.0.6 was to (after backing everything up) put the complete tar.gz file in document root and overwrite existing files. The "patches" broke many, many things, and I had the identical symptoms that you describe.

The only thing that seems to be broken now is the logout button, when SEF is turned on. I get "URL redirection limit exceeded" when I try to log out.

Any ideas on that one?

--
Trevor

dingin

Seems many problem over there, I think I'll stay with 1.0.5 only

__________________
Meet me at dingin.info

Trevor

Good call. I rolled back for now.

SvenErik

The problems with the upgrade to the 1.0.7 release are usually because of human error; they don't upload all the files, they mess with file/folder permissions, they have done some core hacks that mess with the code, they need the SafeModePatch for 1.0.7 which hasn't been released yet but upgrade anyway, they have badly configured servers, etc, etc....

But most people who have upgraded has managed to do so without problems. There were some problems with the 1.0.6 release, but it was fixed very soon with the 1.0.7 release.

And the security risk of continue running with a 1.0.5 release is too big to not upgrade! And since you just made it public to the world that you will continue to run 1.0.5 and giving out your URL in your signature could lead to you being hacked!!! So please reconsider, and upgrade to 1.0.7 ASAP!

__________________
"Every demand is a prison, and wisdom is only free when it asks nothing."
Sir Bertrand Russell

Quizzey

Thankfully I had live support available from me hosting service.

To answer one of my questions above .. you can't check the password of a mysql database. I deleted the original user/password and added a new one and then changed my configuration.php ..... and went back to 1.0.5

Trevor ... I was having heaps of grieve with login out with SEF turned on ... I never checked it with SEF turned off.

Tom

Trevor

Well, I think I'll agree with most of what you have to say, but not everything.

A clean install of 1.0.7 on a well configured FreeBSD server still results in consistently reproducable errors. No show stoppers so far, but annoying things like not being able to log out, or losing the contents of the news article a user is trying to post when using the popup in HTMLarea. These are mostly cosmetic, but annoying.

The risk of being hacked can be mitigated, if I'm reading the info correctly, by implementing some very simple controls on IP address ranges that can access the admin tools (assuming mod_access is compiled into your apache).

If I am missing something, and the security holes are larger and more glaring than I have seen, please let me (and everyone else) know, and I'll roll back up to 1.0.7 and live with (or try to diagnose) the cosmetic problems.

Quizzey

But having read the reply from SvenEric above I guess I'll be upgrading ASAP and sort out any probs that may come along.

Tom