Version 5.5.2.1 manual upgrade
Permalink
Hey,
I was trying to manually upgrade from version 5.5.2.1 to 5.6.0. I downloaded the zip file, unpacked it into the ../updates folder. It now looks like this: ../updates/concrete5.6.0 . I go back into dashboard -> system & settings -> Upgrade & Restore -> Update concrete5. The new package should show up as available for installation but it doesnt. Than I ran the update script manually but all that came back was that my page is up to date on version 5.5.2.1 although the script is supposed to check the update folder.
Anyone an idea what to do?
I was trying to manually upgrade from version 5.5.2.1 to 5.6.0. I downloaded the zip file, unpacked it into the ../updates folder. It now looks like this: ../updates/concrete5.6.0 . I go back into dashboard -> system & settings -> Upgrade & Restore -> Update concrete5. The new package should show up as available for installation but it doesnt. Than I ran the update script manually but all that came back was that my page is up to date on version 5.5.2.1 although the script is supposed to check the update folder.
Anyone an idea what to do?
Unfortunately this is how I feel about 5.6 as well.
I've found that I'm not having any trouble with it as a fresh install, but the upgrade path from 5.5 to 5.6 seems to have lots of bugs and issues. So I'm only upgrading sites as far as 5.5.2.1 and not considering 5.6 stable yet.
Don't get me wrong, I think 5.6 is great, and I have no doubt the bugs will be addressed, but I think there needs to be re-consideration on what is considered 'stable'.
I've found that I'm not having any trouble with it as a fresh install, but the upgrade path from 5.5 to 5.6 seems to have lots of bugs and issues. So I'm only upgrading sites as far as 5.5.2.1 and not considering 5.6 stable yet.
Don't get me wrong, I think 5.6 is great, and I have no doubt the bugs will be addressed, but I think there needs to be re-consideration on what is considered 'stable'.
Are you guys reporting your problems on the bug tracker to make sure the core team is working to resolve your issues?
I tried to manually replace the core already but end up at the same problem. When I run the script it tells me my version is 5.5.2.1.
Thanks for sharing your experience with 5.6! I was hoping that an upgrade would resolve some ssues especially with regards to composer permissions but it might not be worth it. I understand the problem is the upgrade. Do you consider 5.6 good enough to re-install and move my pages manually to the new system?
Thanks for sharing your experience with 5.6! I was hoping that an upgrade would resolve some ssues especially with regards to composer permissions but it might not be worth it. I understand the problem is the upgrade. Do you consider 5.6 good enough to re-install and move my pages manually to the new system?
Hello,
First make sure that all add-ons and themes that you have installed are compatible with 5.6. Either update them to a version that does support 5.6 or remove ones that do not.
Next and most important, make a back up of your database using MySQL.
You do not have to run an update from the /updates directory.
You can simply replace the /concrete directory in the root of concrete5 with the new one.
Rename the /concrete directory in the root of concrete5 to something like /concrete-old
Next move the new /concrete directory that you uploaded to /updates/concrete5.6.0/concrete to the root of concrete5. Be sure to move only the /concrete directory and delete the rest of the files and directories located in /updates.
Now visit this page to run the upgrade script.
yourdomain.com/index.php/tools/required/upgrade
After the update has run successfully, delete /concrete-old
If you have any problems with the update, you can resort back to the database backup and the old /concrete directory.
First make sure that all add-ons and themes that you have installed are compatible with 5.6. Either update them to a version that does support 5.6 or remove ones that do not.
Next and most important, make a back up of your database using MySQL.
You do not have to run an update from the /updates directory.
You can simply replace the /concrete directory in the root of concrete5 with the new one.
Rename the /concrete directory in the root of concrete5 to something like /concrete-old
Next move the new /concrete directory that you uploaded to /updates/concrete5.6.0/concrete to the root of concrete5. Be sure to move only the /concrete directory and delete the rest of the files and directories located in /updates.
Now visit this page to run the upgrade script.
yourdomain.com/index.php/tools/required/upgrade
After the update has run successfully, delete /concrete-old
If you have any problems with the update, you can resort back to the database backup and the old /concrete directory.
A couple of things in addition to Hostco's excellent summary:
If you are trying to repair an automatic upgrade, then you better look in your config/site.php and remove the 'define' line pointing to the updates folder.
Don't delete your 'concrete-old' directory for a while until you're sure you won't need to revert back to it.
I found that most of my upgrade issues were the result of my overrides. If your error message contained a reference to being 'unable to re-define a class', it's usually an override that is clashing with the new architecture. I have to admit that my overrides are usually minor tweaks so I renamed the offending override file and things went well. If I felt it was worth the effort, I would troubleshoot the override on a test system.
If you are trying to repair an automatic upgrade, then you better look in your config/site.php and remove the 'define' line pointing to the updates folder.
Don't delete your 'concrete-old' directory for a while until you're sure you won't need to revert back to it.
I found that most of my upgrade issues were the result of my overrides. If your error message contained a reference to being 'unable to re-define a class', it's usually an override that is clashing with the new architecture. I have to admit that my overrides are usually minor tweaks so I renamed the offending override file and things went well. If I felt it was worth the effort, I would troubleshoot the override on a test system.
Hi
I have just updated two sites from 5.5.2.1 to 5.6.0.2 with out a problem.
I downloaded 5.6.0.2 from concrete to my PC. I created an new folder in mysiteroot/updates called concrete5.6.0.2. I then uploaded just the concrete core folder of C5.6.0.2 to mysiteroot/updates/concrete5.6.0.2.
I backed up the database and then went to dashboard/system/backup_restore/update and selected update. About 15 seconds later the site was updated and is all running as it should be.
I now have a few sites on 5.6 and find it an improvement over 5.5
Colin
I have just updated two sites from 5.5.2.1 to 5.6.0.2 with out a problem.
I downloaded 5.6.0.2 from concrete to my PC. I created an new folder in mysiteroot/updates called concrete5.6.0.2. I then uploaded just the concrete core folder of C5.6.0.2 to mysiteroot/updates/concrete5.6.0.2.
I backed up the database and then went to dashboard/system/backup_restore/update and selected update. About 15 seconds later the site was updated and is all running as it should be.
I now have a few sites on 5.6 and find it an improvement over 5.5
Colin
Don't bother upgrading to 5.6, it has more holes in it than a colander,
I have attempted to upgrade three different sites to 5.6 and after wasting hours of time trying to patch it up decided to stay with 5.5.2.1, at least until a truly stable version is released..