What PHP Version Are You Using as Default?
I am not surprised when I see most of the sites are still running under PHP 5.6. Even when new clients sign up, most of them use 5.6.
I was wondering what is the current trend in setting the default PHP version. Do you set it to the latest or still PHP 5.6?
++++++++++++++
list of top cheapest host http://Listfreetop.pw
Top 200 best traffic exchange sites http://Listfreetop.pw/surf
free link exchange sites list http://Listfreetop.pw/links
list of top ptc sites
list of top ptp sites
Listfreetop.pw
Listfreetop.pw
+++++++++++++++
We have set it to 7.2 by default but user can set it low till 5.6
One Shot Solution - Website Designing and Software Development Company Serving Since 2010
Now Also Offering Quality Shared, Reseller, VPS servers, and Dedicated Servers
https://web.oneshotsolution.com - 18X7 Sales & Support via Phone , Email , Chat and Ticket
PHP 5.6 is insecure now and some customers do use it as their application will not support the 7.x version.
Are you looking for best price for self-managed VPS? See WebProVPS website for more details.
VPS Price Match Guarantee on: All our range of DDOS protected XEN HVM VPS
== Contact us for any online solution development or managed / unmanaged vps hosting ==
Honestly I would have to say it varies per client. For instance one website may use a forum software that is 5.6 only while others like to use the newer ones. Personally though as long as they know how to secure and maintain their website it should be fine regardless but I set mine for my clients as 7.2 by default as the app installer seems to have more want that version.
Fast Reliable Web Hosting Dedicated to beginner users. Cpanel Shared Hosting. https://bhdmmwh2.us/
Many plans and custom plans offered at fair prices.
Proudly hosting customers since 2012.
Currently our default is PHP 7.1. But PHP 7.1 is still technically OK until the first of December. We'll be switching to PHP 7.3 by default before then.
Quote Originally Posted by MechanicWeb-shoss View Post
I am not surprised when I see most of the sites are still running under PHP 5.6. Even when new clients sign up, most of them use 5.6.
This has kind of been the one bone I have to pick with PHP. They need to slow down their release cycle for PHP. Why can't PHP 7.3 have a 5 to 10 year lifetime? Or pick a version and keep it running with a longer life. I get that PHP is a different type of language than say, C or C++ (PHP being intended almost exclusively for online, C and C++ is mostly offline) and so there is a need to keep it updated. But I think there is a huge swath of people that would prefer a stable and long-term PHP solution.
As it stands now, when we switch our default to PHP 7.3 in December... that move will only buy us 2 years as PHP 7.3 is set to go end of life in December 2021.
PHP 7.3
It's the recommended version by WordPress and given that this is most people's go-to, I think it makes sense.
Ethernet Servers Limited - Est. 2013! - sales @ ethernetservers.com
SSD cPanel Web Hosting w/ LiteSpeed, MariaDB, CloudLinux, MultiPHP & JetBackup!
Intel Xeon E5 Virtual Servers w/ KernelCare in NEW JERSEY & LOS ANGELES! (Internap)
Fully Managed cPanel VPS w/ Softaculous, Daily Backups & Pro-Active Monitoring!
This has kind of been the one bone I have to pick with PHP. They need to slow down their release cycle for PHP. Why can't PHP 7.3 have a 5 to 10 year lifetime? Or pick a version and keep it running with a longer life. I get that PHP is a different type of language than say, C or C++ (PHP being intended almost exclusively for online, C and C++ is mostly offline) and so there is a need to keep it updated. But I think there is a huge swath of people that would prefer a stable and long-term PHP solution.
Couldn't agree more.
It is a pain in deed to swith to a newer PHP version every now and then. The main issue is their constant deprecation of some PHP functions for which older scripts no longer run on a recent PHP version.
Quote Originally Posted by ES-George View Post
PHP 7.3
It's the recommended version by WordPress and given that this is most people's go-to, I think it makes sense.
We are considering to set PHP 7.3 as the default. Managing support requests after the switch is going to be an issue. Most of the users do now ant to switch and I do not understand why.
When I developed sites, I used to keep my scripts always updated.
Always update default version to latest version with notification. Customer can switch it back to different version afterwards. Always done it that way.
Good management is to keep using the latest technology features/performance/stability wise. Why should hundreds or thousands of customers have to put up with outdated PHP/MySQL just because several customers are too lazy or forget to make their script compatible with the latest setups? Never had any issues updating the default version to the latest version.
Fast Host - Cloud Hosting w/ LiteSpeed & Imunify360 Security
Backup Storage - Backup Storage w/ SFTP, SSH & cPanel Access
Any new accounts default to PHP 7.1 and anyone previously setup with a different version keep that as their default. While it be ideal to use PHP 7.3 the amount of users who try it and have issues is unfortunately quite high. There are a lot of popular themes and plugins that are simply still not compatible.
This has kind of been the one bone I have to pick with PHP. They need to slow down their release cycle for PHP. Why can't PHP 7.3 have a 5 to 10 year lifetime? Or pick a version and keep it running with a longer life. I get that PHP is a different type of language than say, C or C++ (PHP being intended almost exclusively for online, C and C++ is mostly offline) and so there is a need to keep it updated. But I think there is a huge swath of people that would prefer a stable and long-term PHP solution.
When PHP did this it overall hurt the language. PHP 5.2 was released in 2006 and it wasn't until 2011 that it reached end of life. During this time PHP 5.4, 5.5 and 5.6 were released and a vast majority of applications only guaranteed PHP 5.2 compatibility. This created a situation even after EOL there was still a large amount of applications that only worked on PHP 5.2 At least with this new release cycle and incremental changes it guarantees at least applications work to support the oldest PHP version supported as well as the newest.
Hardened PHP everywhere then it depends on when server is installed and provision is stopped
(native version is disabled)
I usually not trust new version to be stable, before it's 10th 7.3 will be new default at 7.3.10
I myself use PHP 7.3
There is a nice definitive PHP 5.6, 7.0, 7.1, 7.2 & 7.3 benchmark across 24 different platforms/configurations; including WordPress (both 4.9 and 5.0), Drupal, Joomla!, Laravel, Symfony, and ... also popular ecommerce solutions such as WooCommerce, Easy Digital Downloads, Magento, Grav CMS, and October CMS.
Here is the blog URL:
The Definitive PHP 5.6, 7.0, 7.1, 7.2 & 7.3 Benchmarks
Always update default version to latest version with notification. Customer can switch it back to different version afterwards. Always done it that way.
That's the way to go.
While it be ideal to use PHP 7.3 the amount of users who try it and have issues is unfortunately quite high. There are a lot of popular themes and plugins that are simply still not compatible.
I personally haven't used 7.1. Made the switch from 5.6 to 7.3 and didn't have any issue.
For thoise of you running shared hosting servers and offering phpMyAdmin on the plans: You do know that phpMyAdmin not yet support PHP 7.3?:
https://www.phpmyadmin.net/downloads/
Current version compatible with PHP 5.5 to 7.2 and MySQL 5.5 and newer.
We are currently running PHP 7.2.x and waiting for phpMyAdmin 5.0.x wich will have support for PHP 7.3, and also waiting for Drupal 7 to support PHP 7.3: https://www.drupal.org/project/drupal/issues/3012308
We are currently running PHP 7.2.x and waiting for phpMyAdmin 5.0.x wich will have support for PHP 7.3, and also waiting for Drupal 7 to support PHP 7.3: https://www.drupal.org/project/drupal/issues/3012308
Nice find. Thank you for pointing that out.
Why should hundreds or thousands of customers have to put up with outdated PHP/MySQL just because several customers are too lazy or forget to make their script compatible with the latest setups?
It is not lazy customers but in most cases it is themes or templates or plugins which are not compatible with the new php versions and the developers do not update them. So the client has spent money to purchase them and cannot use the new php version because of it. I have seen it PLENTY of times!
99% of my servers are Centmin Mod LEMP stack based with PHP (php-fpm) 7.2/7.3 defaults but I also backport all major security fixes from PHP 7.1/7.2/7.3 to Centmin Mod's PHP 5.6.40 and PHP 7.0.33 binaries. So security wise is relatively ok but performance difference between 7.2/7.3 and earlier versions is quite huge depending on php web app - especially with PHP 7.3 when you use Profile Guided Optimization training for specific PHP web apps can lead to up to 30% better performance than without PGO training! So really you'd want to be on PHP 7.2/7.3 anyway
: CentminMod.com Nginx Installer (Nginx 1.17, PHP-FPM 5.4-5.6, 7.0-7.3 (7.4 ready), MariaDB 10 + optional ngx_pagespeed/lua) for CentOS
: Centmin Mod Latest Beta Nginx HTTP/2 HTTPS supports TLS 1.3 via OpenSSL 1.1.1 or BoringSSL
: Nginx & PHP-FPM Benchmarks: Centmin Mod vs EasyEngine vs Webinoly vs VestaCP vs OneInStack
It is not lazy customers but in most cases it is themes or templates or plugins which are not compatible with the new php versions and the developers do not update them. So the client has spent money to purchase them and cannot use the new php version because of it. I have seen it PLENTY of times!
Yes, it is usually due to laziness or budget which stops them from updating the themes and plugins, but that also comes with a security risk which can cause harmful activity on the server like getting IP blacklisted from spam being sent or phishing emails being sent from the server etc. What you say is no excuse not to update the themes and plugins. If they are not able to update them then maybe they should not have them in the first place.
Fast Host - Cloud Hosting w/ LiteSpeed & Imunify360 Security
Backup Storage - Backup Storage w/ SFTP, SSH & cPanel Access
For thoise of you running shared hosting servers and offering phpMyAdmin on the plans: You do know that phpMyAdmin not yet support PHP 7.3?:
https://www.phpmyadmin.net/downloads/
We are currently running PHP 7.2.x and waiting for phpMyAdmin 5.0.x wich will have support for PHP 7.3, and also waiting for Drupal 7 to support PHP 7.3: https://www.drupal.org/project/drupal/issues/3012308
What specifically isn't working with phpMyAdmin 4.9.0.1 and PHP 7.3? Or are you just saying that it isn't officially supported? Seems to be working for me on DirectAdmin... but I'm really just loading the main phpMyAdmin page.
But... if this is true and phpMyAdmin really doesn't work with PHP 7.3... then this also underscores why it's a bad idea to have phpMyAdmin publicly accessible instead of behind the control panel port. For example, on DirectAdmin, if you have PHP 7.3 as your default version for your accounts, and if phpMyAdmin does not work with PHP 7.3, then if phpMyAdmin was accessible behind the DirectAdmin control panel port (2222) then this would not be an issue. The DirectAdmin control panel web server could run an older version of PHP while the publicly accessible PHP is newer.
It is not lazy customers but in most cases it is themes or templates or plugins which are not compatible with the new php versions and the developers do not update them. So the client has spent money to purchase them and cannot use the new php version because of it. I have seen it PLENTY of times!
So it's lazy developers then?
That's why it's always important to stick to reputable themes and plugins. Just because some guy named Joe created a plugin that does everything you want... doesn't mean that Joe is always going to keep the plugin up to date or tested. What makes a reputable theme and plugin? That's very subjective and you really just have to be your own guide. But if a plugin only has 10 installs and hasn't been updated in 3 years... I'd say it's not very reputable.
Moral of the story... don't give your money to just anyone. If you pay money for a plugin or theme, know what you are getting into.
I also always stick with the latest PHP version for the entire server. Security obviously is always a priority for the entire server and you always need to make sure to stick with the latest updates which for me that is PHP 7.2, but since customers can switch to lower PHP version's as needed. I do have have some still using PHP 5.6. We always do warn customers that they need to upgrade their scripts so they can work with the newer version's but not a lot of customers are able to do it or even right away depending on how their site was built so you always have to give them the options of being able to choose the lower version's.
Yes, it is usually due to laziness or budget which stops them from updating the themes and plugins, but that also comes with a security risk which can cause harmful activity on the server like getting IP blacklisted from spam being sent or phishing emails being sent from the server etc. What you say is no excuse not to update the themes and plugins. If they are not able to update them then maybe they should not have them in the first place.
This is clueless rambling.
If my hosts ever said anything so obscenely nonsensical and insulting, I'd have no qualms about telling the to go f*** themselves, and immediately shift my online properties to other servers. (Or more accurately, do the shifting first, as I would expect an immature reaction from those that would mind vomit such lunacy.)
Please exit your bubble. That's not how the real world works.
|| Need a good host?
|| See my Suggested Hosts List || Editorial: EIG/Site5/Arvixe/Hostgator Alternatives
This is clueless rambling.
If my hosts ever said anything so obscenely nonsensical and insulting, I'd have no qualms about telling the to go f*** themselves, and immediately shift my online properties to other servers. (Or more accurately, do the shifting first, as I would expect an immature reaction from those that would mind vomit such lunacy.)
Please exit your bubble. That's not how the real world works.
No, in my opinion it isn't. If you ran/managed as many sites as other providers do then maybe you'd understand.
What I said applies to VPS/Dedicated servers where CloudLinux is not used i.e outdated PHP versions from cPanel can cause a massive problem even for VPS/Dedicated as it can affect entire subnets/IP ranges if it gets out of control. I'm talking about the customers who don't care about any issues that affect other customers. Fortunately, the majority of customers are considerate. But it only takes a few careless customers to cause trouble for everyone.
FYI OP never mentioned whether the question was for Shared or VPS/Dedicated which does make a difference because of the reasons I mentioned above.
So I will add "don't care" to laziness or budget for one of the reasons customers don't update scripts.
The only one sounding insulting @kpmedia is you for not understanding what I meant. Don't take time to clarify things will you? You gladly want to discuss the topic but go all personal like that. Odd.
I've been on the other side too where I paid a good amount of money for custom development only for the developer to disappear or the business shut shop and then site hacked due to insecure code. Did I leave the insecure code lying around so it affected other customers hosted on the server? No.
Either customer needs to get the code updated or remove it. What else do you suggest? Not so much an issue when using CloudLinux as they patch all of the PHP versions.
What I think is good to do is use the version before the latest version like PHP 7.2 and allow customers to use the version below PHP 7.2 or they can upgrade to the latest version PHP 7.3. There is nothing wrong with that, IMO. It is fine as long as you notfify customers before you update the PHP version.
Also, it would be good if you answered the OP instead of throwing insults around due to you not understanding me. I thought you were more professional than that @kpmedia. Geeez. Why do you sound so angry?
Fast Host - Cloud Hosting w/ LiteSpeed & Imunify360 Security
Backup Storage - Backup Storage w/ SFTP, SSH & cPanel Access
No, in my opinion it isn't.
Your opinion is wrong -- it's based faulty facts/logic.make money through apps
xenoblade 2 make money
d-hosting webmail
ghost forum
members.tubepaki.com
hosting license
traffiktrader.com
magicfinds.com
e- domain geometry
natro hosting forum
End-of-life... schmend-of-life.
I mean... after all... they're just words.
I reject your reality and substitute my own.
FYI OP never mentioned whether the question was for Shared or VPS/Dedicated which does make a difference because of the reasons I mentioned above.
Here, let me clarify your confusion. I thought it is provided that the default PHP version is needed to be setup on dedicated and VPS servers intended to sell shared hosting.
