Updating from v5.4.2.2 -> v5.5.2.1 - HELP!

Permalink
Ok, trying to trouble-shoot an error here...

The site is running fine on v5.4.2.2. My client tried to update using the auto-updater in the dashboard, but it failed (database error). The site went down.

I got the site back up by modifying the config.php file with the version number (setting it back to v5.4.2.2)

I've since fixed the database error, and now have a solid backup of that.

Now when I try to update, I get the following error:

An Unexpected Error occurred while upgrading: mysql error: [1054: Unknown column 'Pages.cIsActive' in 'field list'] in EXECUTE("select Pages.cID, Pages.pkgID, Pages.cPointerID, Pages.cPointerExternalLink, Pages.cIsActive, Pages.cIsSystemPage, Pages.cPointerExternalLinkNewWindow, Pages.cFilename, Collections.cDateAdded, Pages.cDisplayOrder, Collections.cDateModified, cInheritPermissionsFromCID, cInheritPermissionsFrom, cOverrideTemplatePermissions, cPendingAction, cPendingActionUID, cPendingActionTargetCID, cPendingActionDatetime, cCheckedOutUID, cIsTemplate, uID, cPath, Pages.ctID, ctHandle, ctIcon, ptID, cParentID, cChildren, ctName, cCacheFullPageContent, cCacheFullPageContentOverrideLifetime, cCacheFullPageContentLifetimeCustom from Pages inner join Collections on Pages.cID = Collections.cID left join PageTypes on (PageTypes.ctID = Pages.ctID) left join PagePaths on (Pages.cID = PagePaths.cID and PagePaths.ppIsCanonical = 1) where Pages.cID = 0")

And when I use:www.www.mydomain.com/tools/required/upgrade,... I get this:

You must first upgrade your site to version 5.4.2.2

....

I am thinking that the site files have been updated, but since the first update failed, I've got a mis-match in files...

So, how can I fix this, and get the site updated???

Any help appreciated!!!

 
adajad replied on at Permalink Reply
adajad
Was version 5.4.2.2 also an auto-upgrade from an earlier version?
wckadmin replied on at Permalink Reply
No, v5.4.2.2 was a fresh install, site was built on that. I've tried replacing the core c5 files with those of v5.4.2.2, but no luck.

Thanks for the reply.
adajad replied on at Permalink Reply
adajad
When you rolled back, did you also roll back the database (and not just the files and the config edit)?

Have you tried to force the upgrade script to run with 'yourdomain.com/index.php/tools/upgrade?force=1'

If that doesn't work, try this (tedious but safe).

1. Set up a development environment and install a fresh copy of concrete5 v. 5.4.2.2.

2. Copy your files from your backup into your dev install.

3. Import your 5.4.2.2 database backup.

4. Test your site (it should work as before trying to update to 5.5.2.1)

5. Download concrete5 v. 5.5.2.1 and unzip the concrete folder to your dev install (rename or delete your 5.4.2.2 concrete folder before the copy).

6. Go to 'yourdomain.com/index.php/tools/upgrade' and run the upgrade script.

Hopefully your dev installation is now updated to 5.5.2.1 and you can run a full backup and restore to your live site.
wckadmin replied on at Permalink Reply
No, I didn't roll back the database, I'm not sure how to do that.

I'll try those steps you've outlined. Thanks very much.
adajad replied on at Permalink Best Answer Reply
adajad
wckadmin replied on at Permalink Reply
THANK YOU!!

This troubleshooting guide you gave me helped me SOLVE the issue.http://www.concrete5.org/documentation/how-tos/developers/troublesh...

Turns out the site had been updated from v5.4.1.1 -> v5.4.2.2. When I looked at the DB version, it didn't get properly updated. It was still at v5.4.1.1... Which can't update to v5.5.

So the way I fixed this was roll back the core files to v5.4.1.1.

Then I used the auto-update from the dashboard to get everything up to v5.4.2.2. Then I checked the DB version (using phpmyadmin), and it was updated.

And finally I used the auto-update again to go to v5.5.2.1... Everything worked great.

Problem solved, thanks again!
adajad replied on at Permalink Reply
adajad
I'm glad I could point you in the right direction and that the issue has been resolved.