Thread

I’ve installed EE for a client about 4 years ago and now he is asking me to upgrade his build for php5.  What steps do I need to take to make this happen?  The host sent him an email telling his that he is using php4 and now they are upgrading.  I’ve been checking around for about an hour and I haven’t found any solid answers.  I found lots of people having issues with their htaccess file but my install is just a bare build install.  Any suggestions?  Thank you very much!!

-Anthony

Hi Anthony,

EE1.x will run fine on PHP5. Your host upgrading will not affect the existing site. It still meets the requirements.

Does that help?

Hi there,

In relation to this topic, I’ve found that our EE 1.6.9 site is still running on PHP4 (it’s been about 3 years) on our MediaTemple host. If I wanted to upgrade to PHP5, there’s a way to do it through the PHP Settings screen on the hosting account. It gives me 3 options: PHP4, PHP5.2.17 and PHP5.3.8.

Two questions:
1) If I upgrade to PHP5, are there any problems I might run into with my site working correctly?
2) If it’s indeed OK to upgrade without any fallout, which version should I upgrade to? 5.2.17 or 5.3.8?

Thanks very much,
Jenny

Hi Jenny,

You should able to upgrade to PHP 5.2.17 without any issue. If needs be you can always move up again.
Your best adviser will be your host here but EE1.x works in PHP5 regardless

My hosting company just upgraded my server to PHP 5.3.8 (according to a phpinfo file that I just uploaded). I just tried logging into my EE (1.6.x) CP and the CP’s index file is just showing me a blank page. I think that it did display the user login dialogue, and that I logged in—then blankness. Now calling the CP (via the same bookmark that I always use for this task) goes straight to the blank screen.

TBH it’s been about a week since I last logged in to my CP, but it seems like too much of a coincidence that this has apparently happened since the PHP upgrade (which happened yesterday-ish). I’m not certain which version of 1.6 I’m running—normally I’d get that from the CP. I think it’s either 1.6.7 or 1.6.8.

The site itself still seems to be working okay from a visitor point of view, but I can’t get into the CP at all. I’ve tried to get in using Safari 5, Chrome, and Firefox 8 (all on a Mac), all to no avail.

So, um… help?

Hi Rick,

Can you try clearing your cache manually via FTP?
Delete all the folders under system/cache/ bar the index.html file

Also switch on Error Reporting to see if anything appears for the blank page as it is usually a suppressed error

Hi John, thanks for your reply.

I’ve deleted the cache files, but it has made no difference (also restarted Safari and emptied its cache, just in case).

Turning on error reporting on the server and in the two EE files that you mentioned threw back the following errors (the various errors were all duplicated several times – sometimes dozens of times – but I’ve tried to trim them so that each is only shown once. Hope I haven’t trimmed off any unique errors). I have trimmed and amended the file paths here for security.

Deprecated: Function eregi() is deprecated in …/public_html/system/db/db.mysql.php on line 342

Deprecated: Function ereg() is deprecated in …/public_html/system/core/core.template.php on line 2123

Deprecated: Function ereg() is deprecated in …/public_html/system/core/core.template.php on line 2174

Deprecated: Function ereg() is deprecated in …/public_html/system/modules/weblog/mod.weblog.php on line 3836

Deprecated: Function ereg() is deprecated in …/public_html/system/modules/weblog/mod.weblog.php on line 4051

Deprecated: Function ereg() is deprecated in …/public_html/system/modules/weblog/mod.weblog.php on line 4064

Deprecated: Function ereg() is deprecated in …/public_html/system/modules/weblog/mod.weblog.php on line 4078

Deprecated: Function ereg() is deprecated in …/public_html/system/modules/weblog/mod.weblog.php on line 4078

Deprecated: Function ereg() is deprecated in …/public_html/system/modules/weblog/mod.weblog.php on line 4078

Deprecated: Function ereg() is deprecated in …/public_html/system/modules/weblog/mod.weblog.php on line 4091

Deprecated: Function ereg() is deprecated in …/public_html/system/modules/weblog/mod.weblog.php on line 4106

Deprecated: Function ereg() is deprecated in …/public_html/system/modules/weblog/mod.weblog.php on line 4121

Deprecated: Function ereg() is deprecated in …/public_html/system/modules/weblog/mod.weblog.php on line 4296

None of which means very much to me, I have to admit, but then I’m a designer rather than a programmer. To my eyes it looks like a function ereg() that’s used in the code of EE 1.6.x is no longer acceptable to PHP 5.3.8. If that is the case then I guess I’m stuck until I redesign my site for EE2, but that’s not going to be happening for a while.

But maybe I’m misinterpreting the error reports?

Rick,

Can you do a quick upgrade to EE1.7.1 please and that should sort you out. Let us know how you get on

Hi John;

I’ve just gone through all the hoops for updating a site, got to the point where I run the update.php file through my browser, and I see this. Yeah, you see the problem: no link to click. Am I just being even denser than normal and missing something incredibly obvious? Or have I really hit a dead end?

Okay, found the problem with that glitch: for some reason Transmit hadn’t uploaded the updates folder. And it wasn’t pilot error, either, because no matter how many times I dragged it over from local to remote, it *still* didn’t seem to want to copy. In the end I had to manually create a folder named ‘updates’ on the remote server and then copy the contents of the local folder into it.

After which the link to proceed has appeared in the domain/system/update.php page as expected. EXCEPT… it says that I’m about to update to 10.6.8, and I’m supposed to be updating to 1.7.1.

Could the two weirdnesses be connected? Is there a secret, invisible updates folder lurking on the server, unseeable? (I have Transmit set to show hidden files). Any ideas? (I’m going to hit the update link anyway and see what happens—it might just be that Ellis Labs forgot to update the version number in the update page). Fingers crossed, but if anyone has any insight, do please chime in…

Update: all became clear (EE updates in a series of increments, so I simply needed to click OK several times. I’m still having some problems with Better Meta (detailed in this forum thread, but other than that the update went okay and the problem accessing the CP appears to be fixed. Thanks, John, for the guidance there.

Glad that worked for you Rick.

Jenny and Anthony, where do you stand here? Is all ok for you guys?

Hi John,

Thanks for checking in (and sorry for the late response). I haven’t pulled the trigger yet on the update to PHP5, but may be doing so this week. I’ll keep you posted.

Hello jtoast,

Thanks for letting us know.

Cheers,

Update: I’ve updated to PHP 5.2.17 and have not seen any problems so far. Good thing, too, because our hosting service, MediaTemple, will be doing account-wide automatic updates to PHP5 in mid-May.