Manual Upgrade to 5.6... Not!

Permalink
Just performed a manual upgrade from version 5.5.2.1 to 5.6 and when I go to the upgrade page, it tells me I am running the latest version, 5.5.2.1! Very Twilight Zone... I replaced the entire concrete directory as instructed, and the cache had been turned off (I also emptied it to be sure). Anyone else having this issue?

TeKnoZiz
View Replies:
Job replied on at Permalink Reply
Job
Just to confirm:

1. You deleted the /concrete/ folder
2. You replaced it with the /concrete/ folder from a download for 5.6 from C5.org

Or have you placed 5.6 in the /updates/ folder? (eg in /updates/concrete5.6.0/)

Have you run this script:

http://www.your-concrete5-site.com/index.php/tools/required/upgrade
TeKnoZiz replied on at Permalink Reply
TeKnoZiz
Yes, deleted the /concrete/ folder.
Yes, uploaded entire /concrete/ folder from 5.6 install download.
Yes, ran the script (which told me I was still on 5.5.2.1).

Thanks.
Kiesel replied on at Permalink Reply
I am confused, I thought updates go in the /updates folder, so why do you guys talk about deleting the /concrete folder and putting the files in there?
hostco replied on at Permalink Reply
hostco
We have seen this same issue a couple of times now.

Refreshing the upgrade page a couple of times seems to fix it.
TeKnoZiz replied on at Permalink Reply
TeKnoZiz
Sorry, no such luck for us. Tried multiple times on different computers.
TeKnoZiz replied on at Permalink Reply
TeKnoZiz
Update: Repeated the process... same result.
agencecoteo replied on at Permalink Reply
agencecoteo
Do you have take a look in config/site.php to see if you have a DIRNAME_APP_UPDATED constant ? If yes delete it and it should work.
andarys replied on at Permalink Reply
andarys
Did anyone ever figure out how to upgrade concrete5 (C5)from 5.5.2.1 to version 5.6.0.2?
Remo replied on at Permalink Reply
Remo
I'd assume that your configuration file points to a different core outside of /concrete

Can you check the content of config/site.php, is there anything like this in it:
define('DIRNAME_APP_UPDATED', 'concrete5.2.2.1');


If it is, you'd have to remove it before you can replace the actual core in its default location /concrete
jodibean28 replied on at Permalink Reply
jodibean28
I'm having this same exact issue. Trying to manually upgrade from 5.5.2 to 5.6.1.2. I've uploaded the /concrete/ folder multiple times.

I do not have DIRNAME_APP_UPDATED variable or anything like that in the config/site.php file.

When I try to accesshttp://suwanneebike.org/c5/index.php/tools/required/upgrade... it just tells me "Your site is already up to date! The current version of Concrete5 is 5.5.2.1. You should remove this file for security."

This is a little frustrating and I don't see a resolution on this thread?
mkly replied on at Permalink Reply
mkly
Could you try adding
?force=1

to the end of the url?

Best Wishes,
Mike
MrGrowBizz replied on at Permalink Reply
MrGrowBizz
What did you do to fix this as I am upgrading a site for a client and losing my butt! Thanks, Tim
MrGrowBizz replied on at Permalink Reply
MrGrowBizz
Got this fixed! Thanks
lundco99 replied on at Permalink Reply
lundco99
You fixed it and you didn't wan't to share the solution? :)

Please do, because I'm struggling with the very same problem.
lundco99 replied on at Permalink Reply
lundco99
(Double post)
andarys replied on at Permalink Reply
andarys
Just performed a manual upgrade from version 5.5.2.1 to 5.6, one version at a time.
Downloaded the next version to 5.5.2.1 and performed upgrade to that version, then downloaded the next version(s) one at a time and performed the upgrade one at time, until I reached 5.6....
it is not a very creative way, but works and more straight forward.
lundco99 replied on at Permalink Reply
lundco99
But there are no versions in between 5.5.2.1 and 5.6.0. 5.6.0 is the next version. The manual way of upgrading returns a blank page. It's like the config-file and dirname changes before the install script starts, so nothing happens and the website returns blank pages because of that. (Just a guess. The dirname change breaks the website obviously)
JohntheFish replied on at Permalink Reply
JohntheFish
Check the installation page on this site and go straight to the highest version you can upgrade to for each step. Some versions had upgrade bugs, so by doing every single version, you will get stuck on those bugs!