Upgrading from to

Hey everyone!

I'm running into this time and time again and really what it comes down to is just starting with a fresh install but I'm hoping otherwise. I'm trying to update a Concrete5 site that's running off to a and I always get the same ol' error. Here's the error:

Fatal error: Call to undefined method Request::setCurrentPage() in /home/brick/public_html/updates/concrete5.4.2.2/concrete/dispatcher.php on line 166

Now I know how to roll it back, but how do I overcome this error?


View Replies:
JohntheFish replied on at Permalink Reply
I don't think you can do a 1 step upgrade.

Try a clone of the site on a development system. Upgrade to (which then has the new upgrade mechanism), then 5.5.2, then

Probably also worth switching to the plain yogurt default theme while you are testing it, so that any theme/version issues don't confuse the process.
rainmaker replied on at Permalink Reply
Hey JohntheFish!

I was trying to do a step upgrade sadly. I got that error at I'll try switching the theme once I get the staging site up.

Thanks for any tips! :)
SuperNova replied on at Permalink Reply
First of all, did you back up your site + DB?

Remove any updates after in the folder 'upates', accordingly remove any lines like
<?php define('DIRNAME_APP_UPDATED', 'concrete5.x');?>

in 'sites.php'

Try again with a fresh 5.4.2-update (just very next update), if it is working go on like JohntheFish was advising...
rainmaker replied on at Permalink Reply
Hey SuperNova!

Ohhh I know all too well how to roll them back. I've had several clients who have updated and shouldn't have. :)

Anywho, I think I might have got it. Here's what I did:
- Created a developing site. Put on fresh version of 5.4.2 and then put the theme back in.
- Upgraded to and then to

The last two upgrades seemed to be just fine. It was just getting around whatever was causing the big error when I tried to upgrade the first time. Kind of wondering if anyone has had trouble going from 5.4.2 to :-S

Thanks guys for your tips! Really appreciated it.
JohntheFish replied on at Permalink Reply
There was a bug in the upgrader round about 5.4.2.something that didn't work in some environments and had to be manually patched. I think it was, but you would need to look back through the forums to be sure.
rainmaker replied on at Permalink Reply
That would make sense. I've had horrible luck upgrading from that version. Figured it would be worth a try to figure out how to get around it. Thanks!