Now that we are able to provide multi-PHP environments, the ability to deploy EOL versions for PHP is a MUST.
We all know that 5.3 is EOL but we still need it (because our customers need it). If you can't offer EOL versions for PHP you shouldn't have bothered with multi-PHP in the first place because backward compatibility is the main reason that make this feature so useful.
We need multi-PHP to offer BOTH current AND EOL versions. That way, we will be able to keep up with customers that can't upgrade their scripts and to provide current versions for the rest, without having to maintain several servers for every PHP version like now.
Please take this request into consideration.
Thanks in advance!
I like this idea 
Hi all! At this time we are still not planning to add support for end-of-life versions of PHP, but CloudLinux does offer that support. Currently it's unclear how CloudLinux multi-php will work with EA4's implementation of multi-php, but we're hoping that question will be answered by the end of summer. You can read a bit more about that here.
https://www.cloudlinux.com/view-all/entry/beta-easyapache-4-released-for-cloudlinux
While I encourage anyone who would still like to see this request to continue to add their vote, I'm going to go ahead and lock comments on this request at this point. From what I can see we have gotten all of the feedback we need, and will continue the discussion internally. If you have more information to provide, or have any questions, feel free to shoot me an email!
Hi all! At this time we are still not planning to add support for end-of-life versions of PHP, but CloudLinux does offer that support. Currently it's unclear how CloudLinux multi-php will work with EA4's implementation of multi-php, but we're hoping that question will be answered by the end of summer. You can read a bit more about that here.
https://www.cloudlinux.com/view-all/entry/beta-easyapache-4-released-for-cloudlinux
While I encourage anyone who would still like to see this request to continue to add their vote, I'm going to go ahead and lock comments on this request at this point. From what I can see we have gotten all of the feedback we need, and will continue the discussion internally. If you have more information to provide, or have any questions, feel free to shoot me an email!
I beg to disagree with the last comment on the previous feature which lead to the topic being closed. This is actually the only reason to have support for multiple PHP versions, supporting legacy websites...
The initial request demonstrated clearly the use case:
"Example: clients should be able to choose 5.2.11, 5.3 or 5.4.PHP 5.3 break several old scripts, and some server owners can't afford to setup a server for websites running PHP 5.2.x and another for 5.4.x."
I asked specifically for that question and was give the answer that they planned on supporting php 5.2 and 5.3 soon.
It's a shame half-baked feature gets marked as closed loosing all the "i like this idea" and ppl following that feature request, at least for EA3 they made a compatibility package that one could install at own risk after they discontinued support for php 5.2.
Well I sincerely hope CPanel reconsiders this.
I beg to disagree with the last comment on the previous feature which lead to the topic being closed. This is actually the only reason to have support for multiple PHP versions, supporting legacy websites...
The initial request demonstrated clearly the use case:
"Example: clients should be able to choose 5.2.11, 5.3 or 5.4.PHP 5.3 break several old scripts, and some server owners can't afford to setup a server for websites running PHP 5.2.x and another for 5.4.x."
I asked specifically for that question and was give the answer that they planned on supporting php 5.2 and 5.3 soon.
It's a shame half-baked feature gets marked as closed loosing all the "i like this idea" and ppl following that feature request, at least for EA3 they made a compatibility package that one could install at own risk after they discontinued support for php 5.2.
Well I sincerely hope CPanel reconsiders this.
Yeah, it's frustrating that they felt the need to close comments on the previous request to stifle the discussion that existed throughout that request regarding older PHP versions. We can't even post a comment there to point people to the new request. Just a bad, poor thought out, possibly aggressive more on cPanel's part to get us to go away.... well we're not going away and we're still going to ask for at least PHP 5.3 like we've been asking for since the beginning.
Yeah, it's frustrating that they felt the need to close comments on the previous request to stifle the discussion that existed throughout that request regarding older PHP versions. We can't even post a comment there to point people to the new request. Just a bad, poor thought out, possibly aggressive more on cPanel's part to get us to go away.... well we're not going away and we're still going to ask for at least PHP 5.3 like we've been asking for since the beginning.
Thanks for opening this new feature! We didn't close the MultiPHP feature to stifle discussion, that feature was completed and there was nothing new to discuss. The only conversatinos were requesting a new feature of PHP 5.3, which is why I asked for a new request to be opened. Thanks!
Thanks for opening this new feature! We didn't close the MultiPHP feature to stifle discussion, that feature was completed and there was nothing new to discuss. The only conversatinos were requesting a new feature of PHP 5.3, which is why I asked for a new request to be opened. Thanks!
CloudLinux is offering older security patched versions of PHP here: https://www.cloudlinux.com/benefits/multiple-php-versions.php The cPanel team who worked on Multi-PHP has worked with CloudLinux to ensure this functionality remains compatible in newer versions of cPanel.
Its unlikely that we would be able to build enough support to fund and maintain the security of older versions of PHP beyond what PHP is able to do themselves. If this is something that is important to you, please consider supporting CloudLinux's effort by buying their software. Also, I suggest making clear that that is the reason you are buying their software to ensure they are able to continue funding their multi-php project.
CloudLinux is offering older security patched versions of PHP here: https://www.cloudlinux.com/benefits/multiple-php-versions.php The cPanel team who worked on Multi-PHP has worked with CloudLinux to ensure this functionality remains compatible in newer versions of cPanel.
Its unlikely that we would be able to build enough support to fund and maintain the security of older versions of PHP beyond what PHP is able to do themselves. If this is something that is important to you, please consider supporting CloudLinux's effort by buying their software. Also, I suggest making clear that that is the reason you are buying their software to ensure they are able to continue funding their multi-php project.
No one is asking you to maintain the security of older versions. Just supply it as is like EA3 does. To just immediately set this to "Not Planned" is a huge slap in the face to people who believed what you said months ago that PHP 5.3 was coming after the GUI was completed. So you basically lied or just arbitrarily changed your mind with no respect to the people that asked for Multiple PHP 5 versions in the first place.
We shouldn't have to pay addition money to cloud linux just to cover what cPanel was supposed to in the first place.
Please remove the "Not Planned" status and stop going back on what you said in the past and just make the last version of PHP 5.3 available as you're being requested to do since before you even started the Multiple PHP feature.
It boggles my mind on how cPanel doesn't seem to get why people asked for this feature in the first place. It just smacks as pure lazinous on cPanel's part.
No one is asking you to maintain the security of older versions. Just supply it as is like EA3 does. To just immediately set this to "Not Planned" is a huge slap in the face to people who believed what you said months ago that PHP 5.3 was coming after the GUI was completed. So you basically lied or just arbitrarily changed your mind with no respect to the people that asked for Multiple PHP 5 versions in the first place.
We shouldn't have to pay addition money to cloud linux just to cover what cPanel was supposed to in the first place.
Please remove the "Not Planned" status and stop going back on what you said in the past and just make the last version of PHP 5.3 available as you're being requested to do since before you even started the Multiple PHP feature.
It boggles my mind on how cPanel doesn't seem to get why people asked for this feature in the first place. It just smacks as pure lazinous on cPanel's part.
The exact title of the last feature request was "Allow to install multiple PHP 5.x versions", it was not "Allow to only install PHP 5.4 & 5.5 versions". It is so ridiculous it was marked completed when it was not what people asked for.
The exact title of the last feature request was "Allow to install multiple PHP 5.x versions", it was not "Allow to only install PHP 5.4 & 5.5 versions". It is so ridiculous it was marked completed when it was not what people asked for.
Thanks for changing the status. This is a very important issue that I and others have spent the last year+ waiting to happen based on past assurances from cPanel staff that it was going to happen.
Thanks for changing the status. This is a very important issue that I and others have spent the last year+ waiting to happen based on past assurances from cPanel staff that it was going to happen.
I posted a forum thread to help draw attention to this problem. https://forums.cpanel.net/threads/if-you-want-php-5-3-in-easy-apache-4-vote-now.514561/
I posted a forum thread to help draw attention to this problem. https://forums.cpanel.net/threads/if-you-want-php-5-3-in-easy-apache-4-vote-now.514561/
PHP 5.3 went end-of-life in August 2014.
What scripts are still depending on PHP 5.3? Those script developers haven't updated their code to work with a current version of PHP (which doesn't even include PHP 5.4 - which went end-of-life September 2015). Too difficult and too time consuming to update the script's code to work with a current PHP version? That says a lot about where that developer's true concerns are at.
Allowing PHP 5.3 to be run is just asking for trouble. It's telling your customers that you don't care about security and that you are perfectly fine with allowing scripts that can be compromised and cause for abuse on your server.
This same argument can also be made with PHP 5.4, but I'm willing to give PHP 5.4 some leeway since its just been 3 months since it went end-of-life.
Don't like this constant changing PHP environment? Take this discussion up with the PHP developers and tell them you want an LTS for PHP with a much longer lifetime.
PHP 5.3 went end-of-life in August 2014.
What scripts are still depending on PHP 5.3? Those script developers haven't updated their code to work with a current version of PHP (which doesn't even include PHP 5.4 - which went end-of-life September 2015). Too difficult and too time consuming to update the script's code to work with a current PHP version? That says a lot about where that developer's true concerns are at.
Allowing PHP 5.3 to be run is just asking for trouble. It's telling your customers that you don't care about security and that you are perfectly fine with allowing scripts that can be compromised and cause for abuse on your server.
This same argument can also be made with PHP 5.4, but I'm willing to give PHP 5.4 some leeway since its just been 3 months since it went end-of-life.
Don't like this constant changing PHP environment? Take this discussion up with the PHP developers and tell them you want an LTS for PHP with a much longer lifetime.
We also have 1 tiny backoffice platform that requires php 5.3 -- its not really public facing, its password protected, we understand the "risks". Currently we use Cloudlinux for this...but one question i have that remains un-answered (i have asked 3 times in the other feature request).
Does cPanel multi-PHP conflict in any way with the Cloudlinux (6.6+) multi-PHP? And where are the src's stored for the multi versions in regards to the cPanel version of this functionality? Do they use the same locations/modules/etc as Cloudlinux multi-php or must we make yet another stack of versions/modules? Is there anything people need to know if they are already running Cloudlinux so that worlds don't collide in funky ways? Thanks!
We also have 1 tiny backoffice platform that requires php 5.3 -- its not really public facing, its password protected, we understand the "risks". Currently we use Cloudlinux for this...but one question i have that remains un-answered (i have asked 3 times in the other feature request).
Does cPanel multi-PHP conflict in any way with the Cloudlinux (6.6+) multi-PHP? And where are the src's stored for the multi versions in regards to the cPanel version of this functionality? Do they use the same locations/modules/etc as Cloudlinux multi-php or must we make yet another stack of versions/modules? Is there anything people need to know if they are already running Cloudlinux so that worlds don't collide in funky ways? Thanks!
Update your site to run with newer versions of PHP. Highly unlikely cPanel will implement support for an unsupported/end of life version.
Update your site to run with newer versions of PHP. Highly unlikely cPanel will implement support for an unsupported/end of life version.
cPanel, has any further thought been given to making PHP 5.3 available?
cPanel, has any further thought been given to making PHP 5.3 available?
Very disappointing that cpanel do not offer multiple versions of php including php 5.3. Been waiting a while after been told it was coming. Now we need to upgrade the server and noticed Plesk can do it, and cpanel can't . Basically as we have over 70 sites and some website owners do not want to pay to upgrade from php 5.3 when their sites have been running for years without any security issues coming to light. If I force them to change they will go elsewhere. Just the way it is in the real world.
Very disappointing that cpanel do not offer multiple versions of php including php 5.3. Been waiting a while after been told it was coming. Now we need to upgrade the server and noticed Plesk can do it, and cpanel can't . Basically as we have over 70 sites and some website owners do not want to pay to upgrade from php 5.3 when their sites have been running for years without any security issues coming to light. If I force them to change they will go elsewhere. Just the way it is in the real world.
Hi all! At this time we are still not planning to add support for end-of-life versions of PHP, but CloudLinux does offer that support. Currently it's unclear how CloudLinux multi-php will work with EA4's implementation of multi-php, but we're hoping that question will be answered by the end of summer. You can read a bit more about that here.
https://www.cloudlinux.com/view-all/entry/beta-easyapache-4-released-for-cloudlinux
While I encourage anyone who would still like to see this request to continue to add their vote, I'm going to go ahead and lock comments on this request at this point. From what I can see we have gotten all of the feedback we need, and will continue the discussion internally. If you have more information to provide, or have any questions, feel free to shoot me an email!
Hi all! At this time we are still not planning to add support for end-of-life versions of PHP, but CloudLinux does offer that support. Currently it's unclear how CloudLinux multi-php will work with EA4's implementation of multi-php, but we're hoping that question will be answered by the end of summer. You can read a bit more about that here.
https://www.cloudlinux.com/view-all/entry/beta-easyapache-4-released-for-cloudlinux
While I encourage anyone who would still like to see this request to continue to add their vote, I'm going to go ahead and lock comments on this request at this point. From what I can see we have gotten all of the feedback we need, and will continue the discussion internally. If you have more information to provide, or have any questions, feel free to shoot me an email!
Replies have been locked on this page!