update from 5.7 to version 8?

Permalink
Hi,
simple question, but can't find it in the docs, what is the exact rocedure to upgrade from 5.7 to version 8?

allready posted this before as an reply on the docs, and got this:

------------------------------------
VolgensBartjes | Posted on Dec 27, 2016
How to upgrade from 5.7.5.13 to 8? i only see how to upgrade 8 and above, and how to upgrade 5.7.5.10 and earlier?

andrew | Posted on Dec 27, 2016
It's the same process - you just have to make sure your site is updated to the latest 5.7 prior to initiating the upgrade to version 8.
------------------------------------

but you can't choose update in the dashboard as that is "the same process" in the first part ofhttps://documentation.concrete5.org/developers/installation/upgradin... ....
so, is it just downloading version 8, upoad the concrete folder and visiting the website to upgrade? will it take my current blocks, supermint theme and everything to version 8?
just to be sure...
Bart

 
PineCreativeLabs replied on at Permalink Best Answer Reply
PineCreativeLabs
I always do upgrades manually, and these are the steps I take:

1. Download 5.7.5.13, and extract package. Make sure you are already logged in before the next steps!
2. Change the concrete folder name to something like "concrete1", then upload via FTP.
3. Rename the current concrete folder on your server to something like "concrete-old". Rename "concrete1" folder to just "concrete".
4. On the browser, go to: "yourwebsite.com/index.php/ccm/system/upgrade"
5. You should see either an option to upgrade, or it may say it has already been upgraded. Either way, make sure to run the upgrade script, then return to home page to see if everything is working.

To upgrade to 8, do the same as above, but use latest version (8.1).

NOTE: Make sure you have backed up your database prior to doing this!
Also, you will want to remove the old concrete folder, since it won't be needed.

As a recommendation, if your web host supports PHP7, you should use it. This may involve editing the .htaccess file. PHP7 makes Concrete run way faster!
VolgensBartjes replied on at Permalink Reply
@pinecreativelabs i downloaded version 8, unpacked, uploaded, visit domainj.com/index.php/ccm/system/upgrade and see that i'm "allready running 5.7.5.13." :S nothing about version 8? also when clicking the link to /index.php/ccm/system/upgrade?force=1 and then clicking upgrade button, opens /ccm/system/upgrade/submit?ccm_token=1486539493:3763341dd40d50c54678f42d24069f88 but still says that upgrading to 5.7.5.13 is completed :S
VolgensBartjes replied on at Permalink Reply
Anyone please?
Draze replied on at Permalink Reply
Draze
It is the same process ashttps://documentation.concrete5.org/developers/installation/upgradin... I just did the manual dashboard version outlined below.

(Started from 5.7.5.13)

1. Download the latest core fromhttp://www.concrete5.org/download...
2. Unzip the file. Remove all contents except the concrete directory.
3. At this point you should have a folder named something like concrete5.8.x.x, with only a "concrete" directory inside it.
4. Move the concrete5.8.x.x folder into your updates/ directory on the server
5. Head to Dashboard > System and Settings > Update Concrete5 on your website. The update should be listed, and you can click through to update to the latest version.

Then just use the dashboard update to click like twice and you should be good.
jmartinwestern replied on at Permalink Reply
I followed these steps, but there isn't an update showing the settings. Any thoughts on what I missed?
Draze replied on at Permalink Reply
Draze
I don't know what else to tell you.

So you have a folder underneath the updates folder? Structure should look like
updates/
  concrete5.8.1/
    concrete/
    index.html


Also are you sure that you're running the updated version for what you have? You have to be on 5.7.5.12+ I think in order to migrate to 5.8
kaukosaarinen replied on at Permalink Reply
kaukosaarinen
A success story of updating concrete5 from version 5.7.5.13 to 5.8.3.1

After reading reverse experiences of updates I decided to be very, very careful while doing the update. So I tested concrete5 update from the version 5.7.5.13. to 5.-8.3.1 not less than 3 times before doing the same to the live site maintained by me. The last test was to do a full copy of the site onto a sub folder of the current site and do the update there.

There is a very pleasant information in the 8.3.1 Release Notes. ’’Added support for upgrading from older versions of concrete5. Now you may upgrade from 5.7.5.13 all the way to 8.3.1, and from any version in between’’. Brilliant work, thank you very much!

I downloaded manually he latest version 5.-8.3.1 of concrete5 to the updates folder in every case. The update is dated (12-20-2017).

After logging-in do the dashboard update in the control panel where you have the site map and other options. Choose update. The update 5.8.3.1 will be seen. Do the update! If all goes well you will have the update accomplished after a few long minutes…

Further thoughts

Remember to backup your MySQL database and the site, too. The backup is heavily needed if something goes wrong. In the case of problems your site may be lost without backup!

The problem with 30 sec exceeded. This is described carefully in documents. This should be avoided by adding ’’php_value max_execution_time 300’’ to the .htaccess file.

I had this 30 sec problem on my personal test site although I added the code to the .htaccess file. When this occured I simply reloaded the current URL. What happened. The update was accomplished after a new trial and it was working ok! What do nerds and experts say about this?

On the live site and on it’s sub folder there were no problems. First a success with the update on the sub folder. After this I was fairly confident doing the same update for the live concrete5 site.

Thank you very much! Hope someone pondering about doing the update have some help of this.
onemhz replied on at Permalink Reply
onemhz
I followed @simoneast steps from link above few timies and its work perfectly.