PHP & HTTPD Versions

[GatorJacob]

Hello,

cPanel has released PHP 5.2.15 and PHP 5.3.4. We have updated our images, and we will be pushing these versions out this week. We will be testing a few servers tonight, and if all is well, we will be pushing the versions out as follows:

Shared servers will be updated Thursday, 12/16
Reseller servers will be updated Friday, 12/17

[virtvir5]

Thanks a lot for the notification, Jacob. Are you aware whether this will involve any significant changes to the default php.ini settings for either version -- especially extensions, includes and any other path settings?

I ask because I have suPHP_ConfigPath set in my primary .htaccess file as well as a couple of "special" secondaries.

[GatorCarl]

There shouldn't need to be any changes made to existing php.ini files. The extensior_dir path and other settings haven't changed. There were a few security issues that were fixed but overall should be a minor update.

[virtvir5]

Thanks, Carl.

Was aware of the fixed security issues. Just thought cPanel might get around to updating the layout and ordering of their php.ini files which seem to have been based on a php.ini-recommended pattern that is several versions out-of-date even for the 5.2 version.

Oh well. Maybe when they release cPanel 11.28 "stable" next month, if we're real lucky.

[chaloupe]

Thank you very much for the information about the update!

[staralgerie]

Hello,

my PHP version is 5.2.14

is it necessary to do this update?
if yes, how can I upgrade my verision?

thank you

[GatorJacob]

This post is for shared servers only. Do you have a VPS / Dedicated server with us? You can upgrade Apache via the script "/scripts/easyapache".

If you're not comfortable with doing this, you can email support and we can get it upgraded for you as well.

[staralgerie]

Hi,

i have a dedicated server and i have submited a ticket to the support.

i am not comfortable with doing this.

Thank you Jacob

[fuzzfree]

Hello

I hope you do not upgrade shared/reseller servers to php 5.3 without any advance notification (months before upgrade please!).

PHP 5.3 will cause many scripts to stop working!!!

[digitaltoast]

Originally Posted by fuzzfree

Hello

I hope you do not upgrade shared/reseller servers to php 5.3 without any advance notification (months before upgrade please!).

PHP 5.3 will cause many scripts to stop working!!!

Well, you know, 5.3 was release EIGHTEEN MONTHS ago.
How long would you like them to wait before rolling it out?

[virtvir5]

Depends on how many old scripts using "deprecated" functions like ereg() and ereg_replace() they want to break. And the number of people having used cPanel's "QuickConfig" to set up their own configurations based on the 5.2 php.ini-recommended pattern might also be a concern.

[vinay11]

I think this is best way to explain trematodes article.Really i have to say very useful and interesting information,keep up the good work.

Order pizza online mumbai

[CypherOz]

G'Day from Australia! (currently underwater )

Given that PHP V5.2.x is in maintenance only mode and the current stable version is V5.3.x when can we expect shared servers to get PHP V5.3.x?

Refer: http://php.net/

PHP 5.2.16 Released!
[16-Dec-2010] The PHP development team would like to announce the immediate availability of PHP 5.2.16. This release marks the end of support for PHP 5.2. All users of PHP 5.2 are encouraged to upgrade to PHP 5.3.

Thanks!

[quietFinn]

Originally Posted by CypherOz

G'Day from Australia! (currently underwater )

Given that PHP V5.2.x is in maintenance only mode and the current stable version is V5.3.x when can we expect shared servers to get PHP V5.3.x?

Refer: http://php.net/


Thanks!

Currently there are 2 stable releases of PHP

Stable Releases
Current PHP 5.3 Stable: 5.3.5
Current PHP 5.2 Stable: 5.2.17

And PHP 5.3 is already available in HG servers, see here:
http://forums.hostgator.com/php-5-3-...t-t100928.html

[CypherOz]

Thanks, we switched today - looks good so far.

[adityagupta]

Hi

Thanks for sharing this information with us...
It will help in my work..

thanks..



Parking Sensor

[Rockoids]

Originally Posted by digitaltoast

Well, you know, 5.3 was release EIGHTEEN MONTHS ago.
How long would you like them to wait before rolling it out?

If I were them, not for a while. Some scripts, such as the Mambo CMS, have problems with PHP 5.3.

[digitaltoast]

Originally Posted by Rockoids

If I were them, not for a while. Some scripts, such as the Mambo CMS, have problems with PHP 5.3.

Right, so everyone else has to be held back onto old versions of php in case people can't be bothered to apply the Mambo fixes which, according to SVN, were rolled out on
Mon Nov 9 11:09:24 2009 UTC (17 months ago)

As I say, php 5.3 was released nearly two years ago on 30-Jun-2009.

When php 5.2.16 was released as a last-resort emergency patch late last year the announcement said:
http://www.php.net/releases/5_2_16.php

The PHP development team would like to announce the immediate availability of PHP 5.2.16. This release marks the end of support for PHP 5.2. All users of PHP 5.2 are encouraged to upgrade to PHP 5.3.

So, again, I ask just how long you expect hosts to provide support for officially obsoleted versions?

[Rockoids]

And which version are those fixes rolled into?

The latest version of Mambo that's available on their site, 4.6.5, was released prior to the date of the PHP 5.3 fixes. So where's the official patch?

Here's the link to the page where Mambo updates are available. Which one do I look for?

http://mambo-code.org/gf/project/mam..._pkgrls_page=2

[digitaltoast]

Originally Posted by Rockoids

And which version are those fixes rolled into?

The latest version of Mambo that's available on their site, 4.6.5, was released prior to the date of the PHP 5.3 fixes. So where's the official patch?

Here's the link to the page where Mambo updates are available. Which one do I look for?

http://mambo-code.org/gf/project/mam..._pkgrls_page=2

But the point is that, to all intents and purposes, Mambo has pretty much ceased development. I can't think of anywhere that uses it now, the last full release was almost 4 years ago. Many of the mods have been withdrawn after having holes found in them and developers no longer interested.

HG can't really be expected to take account for that, can they?

At some point you gotta move on - Wordpress is a pretty robust CMS now.
There are many other options too, almost all of which have "easy migrate" options from Mambo.

[Rockoids]

I agree with you. But this issue applies to lots of hosts, where there are issues with legacy software that require sticking with PHP 5.2, which is still being updated by the way.

For my colleague to move to WordPress, he'd have to hire a developer to recreate his templates/themes and all the features of his existing site. It's not cheap, particularly since he has a commerce section where he sells products. So the web designer would also have to build a storefront, adding to his cost.

I expect he is not alone. There are loads of people out there who are going to have to upgrade or make expensive changes in their sites to accommodate a PHP upgrade.

[digitaltoast]

Originally Posted by Rockoids

I agree with you. But this issue applies to lots of hosts, where there are issues with legacy software that require sticking with PHP 5.2, which is still being updated by the way.

So when PHP say

"This release marks the end of support for PHP 5.2."

what does that mean?

Originally Posted by Rockoids

For my colleague to move to WordPress, he'd have to hire a developer to recreate his templates/themes and all the features of his existing site. It's not cheap, particularly since he has a commerce section where he sells products. So the web designer would also have to build a storefront, adding to his cost.

I expect he is not alone. There are loads of people out there who are going to have to upgrade or make expensive changes in their sites to accommodate a PHP upgrade.

Probably easier to spend a few minutes just rolling in the patches for 5.3 from CVS?

[Rockoids]

If you mean 5.2.17 is the end of the line, fine, but it doesn't solve the problem.

It also doesn't look as if that PHP 5.3 patch for Mambo is complete or tested.

Remember, too, that a large Web host has to consider the needs of all their customers, many of whom are running older scripts. I expect they'll be conservative in deciding to make the move. I had to downgrade from 5.3 to allow my colleague's site to run.

[digitaltoast]

Yes, this is true. The fact is, unless I've mis-read something, no-one is being FORCED to move to PHP5.3 yet, and even if it becomes the default on HG, you can just switch back to 5.2 via .htaccess

[Rockoids]

Originally Posted by digitaltoast

Yes, this is true. The fact is, unless I've mis-read something, no-one is being FORCED to move to PHP5.3 yet, and even if it becomes the default on HG, you can just switch back to 5.2 via .htaccess

If that is available, no problem. What they might consider doing is leaving PHP 5.2.x as the default, and letting the customer modify .htaccess to 5.3 if they feel that their site is compatible.