Forums

Fatal error: Uncaught exception 'ADODB_Exception'

Permalink
I updated to the latest version of concrete5 everything was working fine, made a few changes to site which I wasn't happy with so decided to backup from an old restore that's when I get the error message (below), the older version would have been on an older version of concrete5 just need to find a way to correct things but now
cant get into my dashboard from the website.

Can somebody PLEASE advise me what to do?

Fatal error: Uncaught exception 'ADODB_Exception' with message 'mysql error: [1054: Unknown column 'logUserID' in 'field list'] in EXECUTE("insert into Logs (logType, logText, logIsInternal, logUserID) values ('exceptions', 'Exception Occurred: /home/sites/kidsmagictricks.co.uk/public_html/magiciansforweddings.co.uk/updates/concrete5.6.0.2/concrete/libraries/3rdparty/adodb/adodb-exceptions.inc.php:78 mysql error: [1054: Unknown column \'ptID\' in \'field list\'] in EXECUTE("select cvID, cvIsApproved, cvIsNew, cvHandle, cvName, cvDescription, cvDateCreated, cvDatePublic, cvAuthorUID, cvApproverUID, cvComments, ptID, CollectionVersions.ctID, ctHandle, ctName from CollectionVersions left join PageTypes on CollectionVersions.ctID = PageTypes.ctID where cID = \'2\' and cvID = \'1\'")\n (1054)\n\n#0 /home/sites/kidsmagictricks.co.uk/public_html/magiciansforweddings.co.uk/updates/concrete5.6.0.2/concrete/libraries/3rdparty/adodb/adodb.inc.php(1037): adodb_throw(\'mysql\', \'EXECUTE\', 1054, \'Unknown column ...\', \'se in /home/sites/kidsmagictricks.co.uk/public_html/magiciansforweddings.co.uk/updates/concrete5.6.0.2/concrete/libraries/3rdparty/adodb/adodb-exceptions.inc.php on line 78
davidwillmott
 
mkly replied on at Permalink Best Answer Reply
mkly
Hi David,
My guess here is that concrete5 is still using the updated *files* but the previous *database*.

When concrete5 updates itself from concrete5.org, it places the new core files in the
/updates

directory of your site. The original earlier versions remain. Then it adds a line to
/config/site.php

That loooks something like
<?php define('DIR_APP_UPDATED', '5.6.0.2'); ?>

at the bottom.

Now here is the part that requires a little investigating/remembering.

Your /updates folder will contain each version that has been updated to and your core /concrete directory will contain the files of the original version you installed.

If this is your first update and your /updates folder only contains one set of files, then you lucked out, and simply delete the DIR_APP_UPDATED entry in /config/site.php and concrete5 will start using the original core /concrete files again.

If this is not your first update then you need to figure out which version of concrete5 you have restored your database from and set the version number in
<?php define('DIR_APP_UPDATED', '5.6.0.2'); ?>

Replace 5.6.0.2 with the version of the restored databse. If you don't know the version of your database you should find it in that database's "Config" table in the field SITE_APP_VERSION.

So don't worry, your almost there.
davidwillmott replied on at Permalink Reply
davidwillmott
Thanks mkly

Much appreciated site back up, thanks for taking the time to help out.
mkly replied on at Permalink Reply
mkly
Not a problem. Glad to hear that you're back up and running.

Best Wishes,
Mike
zoinks replied on at Permalink Reply
This just happened to me and all I did was go into PHPMyAdmin and click "repair tables" and it is fixed.

Make sense? Nothing changed over the last several months so I don't know why I got this error, but I fixed it brainlessly just by repairing the tables.