Exactly the best way to upgrade to 5.7 from 5.6.3.1 ?
Permalink
I've encountered the problem that during upgrading concrete looks for class Exception.php.
than, after I TEMPORARY REMOVE that line that throws the excpetion, concrete looks for app.php in the wrong directory.
I stopped that procedure, seems wrong.
I need the exactly correct procedure, maybe I miss something.
I followed these instructions:
1)https://github.com/concrete5/concrete5-5.7.0/
and
2)http://www.concrete5.org/community/forums/installation/how-to-manua...
I have also upload to my local server a full vendor folder.
Thank you to all.
than, after I TEMPORARY REMOVE that line that throws the excpetion, concrete looks for app.php in the wrong directory.
I stopped that procedure, seems wrong.
I need the exactly correct procedure, maybe I miss something.
I followed these instructions:
1)https://github.com/concrete5/concrete5-5.7.0/
and
2)http://www.concrete5.org/community/forums/installation/how-to-manua...
I have also upload to my local server a full vendor folder.
Thank you to all.
There is currently no way to upgrade from 5.6 to 5.7. In the future it's likely the upgrading will be more like a migration from one 5.6 to a clean 5.7 install, importing the content into the new install – rather than an in-place upgrade on top of 5.6.
The github should be updated then Andrew. It is worded there as to lead people to believe there is an upgrade process.
Also, any addon's/packages you use will need to be upgraded / modified in order to get them to work with the 5.7 code. Typically these are just small touches that need to be made to the php files to get them working again but if you have any of these it will need to happen or they simply won't work.
If that would be created on top of the existing content generator, it would be pretty incomplete. Quite a few permission related settings are ignored and lots of (community) blocks don't properly implement $btExportTables and $btExportPageColumns etc.
I feel that this would be a pro-dev only migration path. Lots of missing things wouldn't be noticed at first and later, it would be too late and users would have to re-create all their permissions settings.
I strongly believe we should put quite some effort into this, at least if we don't want to get rid of lots of existing concrete5 users.
I feel that this would be a pro-dev only migration path. Lots of missing things wouldn't be noticed at first and later, it would be too late and users would have to re-create all their permissions settings.
I strongly believe we should put quite some effort into this, at least if we don't want to get rid of lots of existing concrete5 users.
Is there even any documentation on $btExportTables and $btExportPageColumns?
afaik, no
Hello!
At this time, can we have a way to migrate content from previous versions to 5.7?
Thanks
hv
At this time, can we have a way to migrate content from previous versions to 5.7?
Thanks
hv
Thank you all, all your replies were useful for me : )
This is the problem with them saying on the dowload page "The new version of concrete5 is here!" and not warning people to not try to upgrade their sites. This version simply isn't ready to use on a live site. Do a new install, play with it, write some packages with it, but don't use it on a live site!
We are running a huge expectation for this release. Thats why.
This guys are really awsome! C5 is so powerfull! Thank you c5 team.
This guys are really awsome! C5 is so powerfull! Thank you c5 team.
This is true. We have updated the download page to be clearer. We are working on the migration script as well. Thanks for your patience jumping in as an early adopter of the new release.
Is there anyway to contribute to the migration script / any list of required features etc on what we want to and can't import?
Not quite yet, but probably soon. We'll post something on github when we have it starting to come together. It will likely be a set of packages, one for 5.6 and one for 5.7
Hi Andrew, I was just wondering if there was any further updates on a migration script?
@xigo
Here is the GitHub discussion dealing with migration.
https://github.com/concrete5/concrete5/issues/1991...
Here is the GitHub discussion dealing with migration.
https://github.com/concrete5/concrete5/issues/1991...