Upgrade from 5.6 to 5.7
Permalink
Can 5.6 be upgraded to the latest version of 5.7 without first upgrading to the intermediate versions? I currently have 5.61. I want to go to the latest version. Can anyone tell me how to do this, or where to find instructions?
Thank you for your quick response.
I realize you can't go directly. I'm looking for instructions on what I need to do. I imagine I back up my database, download and install the new version and then what, copy and paste stuff into it? Then delete the old installation? I figured someone has already provided detailed instructions but I can't find any. Can you point me in the right direction? Thanks.
I realize you can't go directly. I'm looking for instructions on what I need to do. I imagine I back up my database, download and install the new version and then what, copy and paste stuff into it? Then delete the old installation? I figured someone has already provided detailed instructions but I can't find any. Can you point me in the right direction? Thanks.
5.6 and 5.7 are quite different in terms of the underlying code, so it's not just that an upgrade script hasn't been written, it's that packages and themes aren't directly compatible.
If you have a 5.6 site and you want to update it to 5.7 the process is to treat your 5.6 site as just a source of content.
You'll need to create a new 5.7 site, create your pages and place your previous content into it. You can't copy in the previous blocks and theme(s), you'll need to either install equivalents for 5.7 and update or change your theme. I've updated a few custom 5.6 themes to be 5.7 ones without too much trouble, but you'll need to familiar with creating themes.
If you have a moderately complex site, you may be better sticking with 5.6, and updating it to the latest in the 5.6 stream. 5.6 is still awesome and if there are no major features in 5.7 that you really need, there's not real necessity to upgrade to it.
If you have a 5.6 site and you want to update it to 5.7 the process is to treat your 5.6 site as just a source of content.
You'll need to create a new 5.7 site, create your pages and place your previous content into it. You can't copy in the previous blocks and theme(s), you'll need to either install equivalents for 5.7 and update or change your theme. I've updated a few custom 5.6 themes to be 5.7 ones without too much trouble, but you'll need to familiar with creating themes.
If you have a moderately complex site, you may be better sticking with 5.6, and updating it to the latest in the 5.6 stream. 5.6 is still awesome and if there are no major features in 5.7 that you really need, there's not real necessity to upgrade to it.
Thank you for your quick reply.
My web host is Host Gator. Are there things I have to do with them also? Anything in the file manager I need to do? I realize I'll eventually need to delete my old C5 installation, right?
Also, I'll need to release my current theme and add-ons from my old site and apply them to my new one, right? And I guess I do all of that in the project page? Will they work with 5.7? I need to check them to see their compatibility.
I'm obvious new to all this. I was really hoping someone had already posted a step-be-step instruction somewhere.
You mentioned good reasons for just staying with 5,6. But aren't they going to stop supporting it soon? My content editor has been weird lately and I thought that might be why. Is this a possibility? Also, my little site is only half done so I thought it might be the right time to take the plunge instead of having to redo a lot of content.
My web host is Host Gator. Are there things I have to do with them also? Anything in the file manager I need to do? I realize I'll eventually need to delete my old C5 installation, right?
Also, I'll need to release my current theme and add-ons from my old site and apply them to my new one, right? And I guess I do all of that in the project page? Will they work with 5.7? I need to check them to see their compatibility.
I'm obvious new to all this. I was really hoping someone had already posted a step-be-step instruction somewhere.
You mentioned good reasons for just staying with 5,6. But aren't they going to stop supporting it soon? My content editor has been weird lately and I thought that might be why. Is this a possibility? Also, my little site is only half done so I thought it might be the right time to take the plunge instead of having to redo a lot of content.
I realize that there is no simple way to migrate the themes, packages and your own code.
But it is manageable to revise/update your own code to 5.7+
But it is NOT manageable to migrate several thousands of pages manually as I have seen mentioned in several posts as the only way to update.
One of the reasons we chose Concrete5 (as opposed to e.g. Joomla) was the excellent update paths - at least up to 5.6.3.3
The existing users are left in a limbo - because how long will the 5.6 version be maintained?
In the end a migration from 5.6 to 5.7+ is essential - and we need a relatively secure way to do that.
If we could "just" migrate at the database level (basically the content), that would help immensely.
I haven't looked into 5.7 yet (because of the above statement regarding no migration possible) - but is the overall concept changed that much?
Isn't it still about Pages, Areas, Blocks, Stacks etc.?
And wouldn't it be possible to perform such a migration of the pages and their content?
We have a multilingual site (4 languages) with more than 4000 pages - and manually rebuilding these in a 5.7 site involves too many resources (time, money, persons, etc.)
But if content could be migrated, then it would be possible to upgrade our own code, and possibly find ways to either replace packages or update them.
I really do like Concrete5, but I would also like it to be easy to stay up-to-date with feature updates, security updates, bugfixes etc.
Best Regards,
Lars
But it is manageable to revise/update your own code to 5.7+
But it is NOT manageable to migrate several thousands of pages manually as I have seen mentioned in several posts as the only way to update.
One of the reasons we chose Concrete5 (as opposed to e.g. Joomla) was the excellent update paths - at least up to 5.6.3.3
The existing users are left in a limbo - because how long will the 5.6 version be maintained?
In the end a migration from 5.6 to 5.7+ is essential - and we need a relatively secure way to do that.
If we could "just" migrate at the database level (basically the content), that would help immensely.
I haven't looked into 5.7 yet (because of the above statement regarding no migration possible) - but is the overall concept changed that much?
Isn't it still about Pages, Areas, Blocks, Stacks etc.?
And wouldn't it be possible to perform such a migration of the pages and their content?
We have a multilingual site (4 languages) with more than 4000 pages - and manually rebuilding these in a 5.7 site involves too many resources (time, money, persons, etc.)
But if content could be migrated, then it would be possible to upgrade our own code, and possibly find ways to either replace packages or update them.
I really do like Concrete5, but I would also like it to be easy to stay up-to-date with feature updates, security updates, bugfixes etc.
Best Regards,
Lars
The current latest version for 5.6 is 5.6.3.3, There is no direct migration to 5.7 at this time.