update from 5.4.2.2 to 5.5.2 gone wrong
Permalink
I was at 5.4.2.2 and upgraded to 5.5.2
The upgrade said it was successful, the next time i logged in I noticed every site page and the dashboard had fatal errors.
I then changed the site.php config back to 5.4.2.2
That got the site running correctly again, but after logging in the dashboard seems to be using the 5.5.2 database. Attached screenshot.
Most pages all of the dashboard pages are blank like the attachment shows.
How do I attempt the upgrade process again now?
My database backup was created from the dashboard backup and not downloaded from the server. I also have a backup of all the files before the upgrade started.
Thanks
The upgrade said it was successful, the next time i logged in I noticed every site page and the dashboard had fatal errors.
I then changed the site.php config back to 5.4.2.2
That got the site running correctly again, but after logging in the dashboard seems to be using the 5.5.2 database. Attached screenshot.
Most pages all of the dashboard pages are blank like the attachment shows.
How do I attempt the upgrade process again now?
My database backup was created from the dashboard backup and not downloaded from the server. I also have a backup of all the files before the upgrade started.
Thanks
While you have reverted the code to 5.4.2.2, you have not reverted the databse. To get back to 5.4.2.2, you need to restore the database from the backup you took before attempting the upgrade.
That is the problem because the system and maintenance pages are all not found. I tried going there with a url but the pages are not there to restore from backup. The backups were encrypted.
I had a similar problem upgrading from 5.4.2.2 to 5.5.2
I was able to resolve the problem by amending the item_list.php at line 514 it should look like this:
the file is located at root/updates/concrete5.2.2/concrete/libraries/
NOTE the /updates/ folder
I am of course assuming you updated your concrete installation using the updates folder?
Don't forget to reset your site.php file to concrete5.5.2
Good Luck.
I was able to resolve the problem by amending the item_list.php at line 514 it should look like this:
public function sortByMultiple() { $args = func_get_args(); $this->sortByString = implode(', ', $args); } }
the file is located at root/updates/concrete5.2.2/concrete/libraries/
NOTE the /updates/ folder
I am of course assuming you updated your concrete installation using the updates folder?
Don't forget to reset your site.php file to concrete5.5.2
Good Luck.
I think I finally got it.
I tried so many things to fix this that it's hard to explain, but here's the best I can do..
I created a new directory on the server to test on.
unzipped a backup copy of the site to it, deleted everything except themes, files and packages.
uploaded a new copy of c5 5.4.2.1
unzipped that, logged in and restored my database backup.
updated c5 to 5.4.2.2 which solved this error: mysql error: [1054: Unknown column 'arIsGlobal' in 'where clause'] in EXECUTE("select arHandle from Areas where arIsGlobal = 1 and cID = '209'")
unchecked use pretty url's that fixed the page not found errors.
copied the password salt from the old site to the test site, that fixed the admin not able to login problem
I certainly didn't do all of that right the first time. but those steps got it back to normal.
I tried so many things to fix this that it's hard to explain, but here's the best I can do..
I created a new directory on the server to test on.
unzipped a backup copy of the site to it, deleted everything except themes, files and packages.
uploaded a new copy of c5 5.4.2.1
unzipped that, logged in and restored my database backup.
updated c5 to 5.4.2.2 which solved this error: mysql error: [1054: Unknown column 'arIsGlobal' in 'where clause'] in EXECUTE("select arHandle from Areas where arIsGlobal = 1 and cID = '209'")
unchecked use pretty url's that fixed the page not found errors.
copied the password salt from the old site to the test site, that fixed the admin not able to login problem
I certainly didn't do all of that right the first time. but those steps got it back to normal.
If are thinking of updating.....
I would wait for the new release of 5.5.2.1 to be released (very soon) as there are a few bugs in 5.5.2
Well Done at getting it sorted out!
I would wait for the new release of 5.5.2.1 to be released (very soon) as there are a few bugs in 5.5.2
Well Done at getting it sorted out!
Thanks, I tried upgrading again on the test server and I got the fatal error again.
Fatal error: Call to a member function getCollectionID() on a non-object in /home/iroqfair/public_html/fix/blocks/autonav/controller.php on line 260
I'm using custom autonav templates that exclude certain pages from the menu. This of course worked on 5.4.2.2
Fatal error: Call to a member function getCollectionID() on a non-object in /home/iroqfair/public_html/fix/blocks/autonav/controller.php on line 260
I'm using custom autonav templates that exclude certain pages from the menu. This of course worked on 5.4.2.2
Concrete 5.5.2.1 has not been released yet (next week I think)
Concrete 5.5.2 has several bugs that will be fixed in the updated release,
However, you could get the latest updates by going to github herehttps://github.com/concrete5/concrete5... download the package from there,
Once you have the package unzipped, open the "web" folder and replace your existing root/updates/concrete5.5.2/concrete/ folder with the downloaded concrete folder,
Remember that your concrete5.5.2 package is (or should be) in your root/updates folder.
However, if this is only on a test server, I would wait a few more days for the official update to be released..
Concrete 5.5.2 has several bugs that will be fixed in the updated release,
However, you could get the latest updates by going to github herehttps://github.com/concrete5/concrete5... download the package from there,
Once you have the package unzipped, open the "web" folder and replace your existing root/updates/concrete5.5.2/concrete/ folder with the downloaded concrete folder,
Remember that your concrete5.5.2 package is (or should be) in your root/updates folder.
However, if this is only on a test server, I would wait a few more days for the official update to be released..
