Thread

Hi there

I’m attempting an upgrade from 2.1.3 to 2.5.2. After hanging for about 25mins at

Please Stand By…
We are currently updating your ExpressionEngine installation.
Do not close your browser until the update routine is finished.
2.3.1

The browser screen is flickering maniacally and progress appears to have stopped.

I have checked my config.php file wherein the version appears to be 240.

What can I do to quickly address this situation?

thanks
David

Update…

The good news is that the update process completed. I should have been more patient.

The bad news is:

I’m now getting a 500 error for every page on the site. Having switched on the Error reporting in admin.php and in index.php I got the following error message (I’ve switched it back off, and I’ve changed the system folder name below)

Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING in /usr/local/pem/vhosts/133872/webspace/httpdocs/mysystem/expressionengine/libraries/Functions.php on line 1197

The line in question is

$segment_one = (isset($segs['0'])) ? $segs['0'] : 'default';

I’m very badly in need of help here. Any guidance is much appreciated.

thanks

Hi David,

That’s not a usual error, so I really wouldn’t recommend we start troubleshooting here. Instead, restore a backup of your site’s files and database, make sure all the data is sound, and let’s start again. I would highly recommend giving this wiki entry a good read.

Thanks Kevin,

I restored my backup and I might revisit again, on a local install.

Do you think that there would be any advantage of incrementally updating the site through a few versions? The real trouble seemed to start with 2.2.0 — that’s when things started to act strangely. I’ve upgraded before on another site on the same host with the same package, with no trouble.

I have quite a few add-ons on the site as well. In your experience, should I upgrade the add-ons to the latest version, and then upgrade EE; or the other way around?

thanks for your help,
David

Morning David,

No, I don’t think doing it in stages will really help.  Though it might help narrow down what seems to be tripping it up.  It’s odd, though.  None of those updates are particularly onerous db wise.  It wouldn’t hurt to truncate your sessions table if it’s huge, but I don’t really see why that would be problematic for the given changes.

It definitely updated the config file when you ran it?  And ended up with 2.5.2? 

As to the addons- I update EE first, and then the addons. 

What I think I’d do given the above- update as normal on the local install (or the live, as long as you keep two databases and keep your old system folder up there- I used to could roll back in about 2 minutes that way).  If you have a slow update again?  Do some spot checks that the table changes were made correctly.  So for example, 220 has this query:

$this->EE->db->query("CREATE INDEX group_name_idx on exp_template_groups(group_name)");

Double check there’s an index on group_name_idx- if so, you know things ran correctly there.

If that php error crops up again?  It’s a weird one, and I see nothing wrong w/that line of code.  So we’d need to dig in to why it’s happening (honestly seems unrelated to the db) and get it squared away.  Which we’re happy to do. 

So- local test seems a good idea since you ran into issues before.  Only negative with a local is we can’t go in for a closer look if needed.  But we could cross that bridge when we come to it.

Hi Robin,

thanks for following this up. Yes – it did update the config to 2.5.2.

I’ve now got the two system folders online and two databases, so when I get a chance I will try again. It might not be for a few weeks. Is it ok if I check back here when I’m planning to do so?

thanks
David

Sounds like a good plan- I’ll leave this one open in case it’s more convenient to post to this existing thread.  The two db/two folders approach on a live sever would make it pretty easy for us to go in and debug if needed.