There was a problem with our server this evening, I'm not sure what yet. When it came back I had to repair the tables and posts before the forums would work again. I was then able to post as admin.

I then became a user to see if they could post and I was presented with this message:

Database error only visible to forum administrators

I could then not log back in as admin and am now shown this:

Fatal error: Call to a member function error() on a non-object in /home/vhost/domain.com/html/libs/mysql.inc.php on line 210

Any ideas as to what I can do to fix this please

Well, the SQL error is only available to admin's; so you'll need to get the content of the error to see what the problem is; you can do this by either enabling sql logging in the control panel or theres a "tick" in the /libs/mysql.inc.php file to show errors to all users (just search for error i think)

Thankyou Gizmo. I cannot get into the control panel now

I edited the file and now I get this message:

Fatal error: Class 'sql' not found in /home/vhost/domain.com/html/libs/ubbthreads.inc.php on line 115

Parse error: syntax error, unexpected $end in /home/vhost/domain.com/html/libs/mysql.inc.php on line 40

From admin screen:

Fatal error: Call to a member function error() on a non-object in /home/vhost/domain.com/html/libs/mysql.inc.php on line 210

From users screen:

Script: /home/vhost/domain.com/html/libs/ubbthreads.inc.php
Line#: 2026
SQL Error: Table 'ubbt_CACHED_PERMISSIONS' is marked as crashed and should be repaired
SQL Error #: 1194
Query: delete from ubbt_CACHED_PERMISSIONS where CACHED_TIMESTAMP < '1183295190'

What exactly did you do to mysql.inc.php?

By changing:
$showerror = 0;

to:
$showerror = 1;

it should not throw ANY errors other than the anticipated mysql errors...

just changed 0 to 1

It then shows users:

Script: /home/vhost/domain.com/html/libs/ubbthreads.inc.php
Line#: 2026
SQL Error: Table 'ubbt_CACHED_PERMISSIONS' is marked as crashed and should be repaired
SQL Error #: 1194
Query: delete from ubbt_CACHED_PERMISSIONS where CACHED_TIMESTAMP < '1183295190'

Run this query from your admin center in database tools, if you can't access your CP, use PHPMyAdmin (or some other similar MySQL database tool) and run the following command:

Done. Received

threads.ubbt_CACHED_PERMISSIONS repair status OK

but still no joy

I believe that data is just temporary, so you could try removing the offending lines:
DELETE FROM `ubbt_CACHED_PERMISSIONS` where `CACHED_TMESTAMP`=1183295190

I got this Gizmo:

Error

SQL query:

DELETE FROM `ubbt_CACHED_PERMISSIONS` WHERE `CACHED_TMESTAMP` =1183295190

MySQL said: Documentation
#1054 - Unknown column 'CACHED_TMESTAMP' in 'where clause'

that's because TIMESTAMP includes an I somewhere between T and M

I may have typed that in manuall vs copy and paste ;)...

Missed that one myself!

Still doesn't work with the I

The hosts have said:

The issue seems to be that the /home/vhost/html/libs/mysql.inc.php file is of zero length - I believe this would contain the relevant sql class that is reporting the error.

Upon checking the following additional files are also zero bytes in size.

./images/moods/default_dark/index.html
./images/moods/default/index.html
./images/forumimages/default/index.html
./images/avatars/default/index.html
./sessions/index.html
./sessions/index.htm
./cache/index.html
./cache/index.htm
./libs/mysql.inc.php
./includes/privacy.php
./includes/header-insert.php
./includes/intro_102.php
./includes/index.html
./includes/boardrules.php
./includes/coppainsert.php
./includes/intro_8.php
./templates/compile/index.html
./styles/index.html

mysql.inc.php has been uploaded and the forums have returned but she's very slow

The only problem with their answer is that you got sql errors. If mysql.inc.php had been empty, you would have gotten no sql errors, since you would not have even known to talk to the database.

In short, their answer could not have possibly caused the original error.

Agreed with ian.

As for 0 length fiels, all of the index.html files should be 0 length, so you actually only have to worry about:


And even then, the only stock one that would be required is the mysql.inc.php which as ian said, couldn't have been the original error; possibly when you edited the file and you uploaded it to the server it choked