Upgrading older Concrete 5 installation

Permalink
Hello everyone,

I'm currently running Concrete 5.4.2.1. This version seems to have problems with the PHP framework 5.4 and above, so I decided to upgrade this installation.

I used the method described in this website:
http://www.concrete5.org/documentation/developers/5.7/installation/...

I downloaded a new version and replaced my concrete directory with a new one. I get to the installing screen of Concrete 5 just fine, but then, instead of giving me an upgrade screen, it gives me an install screen, asking basics like the name of my website and whether I would like to install an empty website or use a template.
This seems wrong to me, as it should upgade my existing installation, not overwrite it with a new one.

I probably did something wrong, like overwrite a config file. If it helps, I renamed the old concrete folder to something else and then added the new folder. Maybe that's the problem?

Can anyone give me guidance on how to fix this so my site gets upgraded, not reinstalled, because I fear I would lose all content currently in the website.

 
goodnightfirefly replied on at Permalink Reply
goodnightfirefly
Before you do anything else, backup your site database (this contains the actual content of your site).

Your safest choice would probably be to restore the previous /concrete folder you renamed, then through the dashboard find the database backup section (5.4.x is a much older version than I'm used to so I can't guide you further on that part sorry).

Alternatively you can use phpmyadmin to export a copy of the database (available in your web hosting panel).

Following that, you should find the Update Concrete5 section in your site dashboard, and you should be able to update your site through there. It should inform you that a newer version is available, it will ask if you would like to download and install it.

You will have to do this several times as each update may/will make important database changes. Eventually you should reach version 5.6.3.3, which is the furthest you can go.

Version 5.7.x (which is the version you were following in that installation guide you linked) is not available to update to from old sites, it is for new sites only.

The reason being, it was completely rebuilt and just isn't feasible to automate an update (its the first time ever this has happened for Concrete5). If you wonder why you can't update from 5.4.x to 5.7.x based on the version numbers, its because 5.4.x means Concrete5 v4, and 5.7.x is Concrete5 v7.

Post back with any issues you encounter and we can guide you further. Good luck!
StevenLemmens replied on at Permalink Reply
Thanks a lot for the clarification. I guess I'll have to update manually through all the versions.

Is it necessary that I do all the versions,
ie:
5.5.2
5.5.1
5.5.0

or can I just do:
5.5.0
and 5.6.0 and skip the intermediary releases?

Also, I unfortunately can no longer get into the dashboard, as this prints just a page of PHP errors. The problem, apparently was the server's upgrade of PHP framework. So I'll have to do the update manually, I guess.
goodnightfirefly replied on at Permalink Reply
goodnightfirefly
Some web hosts allow you to change your PHP version through your cPanel page, if that is available to you then you can try switching to PHP 5.3.

If that isn't available or doesn't allow you access to the dashboard still, you can try exporting your database and website files to your own computer, and run a server (with an older version of PHP such as 5.3) on your own computer in order to update the site.

An older version of XAMPP (local server) that might work for you: http://sourceforge.net/projects/xampp/files/XAMPP%20Windows/1.6.8/...

It is potentially a confusing process for a beginner, post back if you encounter any problems.

==========

Something else to consider, since you are using such an old version, is to rebuild the site using either the newest 5.7 version, or the 5.6.3.3 version you're trying to update to.

You would have to manually copy over your sites content page by page, but in the long run it may be 'easier'. Some themes/addons you are currently using might not be available so you will have to investigate that.

I'd probably recommend this actually, instead of the update route.