PHP upgrade

*daniel77* · 04-02-2018, 04:30 AM

I've recently installed WooCommerce and the Yoast SEO plugin and both keep prompting me that things will run much faster and safer with a PHP upgrade of 5.6 or greater. Is that something that is coming? I presume that this is beyond my abilities as a site owner? Thanks!
"Dear host,

I’m running a WooCommerce webshop on one of your servers and WooCommerce has recommended using at least PHP 5.6. WordPress, the content management system that WooCommerce uses, has listed PHP 7 as the recommended version on n their requirements page: https://wordpress.org/about/requirements/

Can you please let me know if my hosting supports PHP 5.6 or higher and how I can upgrade?

Looking forward to your reply."
I am also getting prompted about setting my PHP memory higher by WooCommerce from 13 MB to 64 MB. Is this something that I can control or is this limit set by y'all. Sorry if these are newbie questions, but, I'm a newbie, so...
Frankly these things are all beyond my understanding, but I am having loads of issues getting WooCommerce to work and I'm trying to iron out all the wrinkles to see if one of them is to blame.

Arthur · 04-02-2018, 04:35 AM

You can upgrade to PHP 5.6 (newer versions will be coming) by going into the CNC Control Panel, Server Info -> Change PHP version

*daniel77* · 04-02-2018, 05:31 AM

Done. Thanks. What about increasing the PHP memory to 64 MB? Also being prompted to upgrade SQL to 5.6. How do I go about doing that, or can I?

**Kevin** · 04-02-2018, 10:23 AM

Before we can upgrade to MySQL 5.6 (from 5.5) we will have to force all the users who haven't yet to upgrade their password hash to the newer format as the old one isn't supported anymore. PHP 5.6 also requires this so that has been a big driving force in getting it done but there are still 39.2% of users on the old hash.

Eventually we will post a final warning (with a week or so notice) and email everyone affected but we are hopeful that the number of affected users will be smaller when we do.

*hobbes* · 04-02-2018, 11:09 AM

A heads up that with MySQL 5.7.5+, they've enabled the ONLY_FULL_GROUP_BY MySQL option by default to make it SQL compliant. If you have GROUP BY clauses that do not specify all ungrouped fields in the SELECT, an error will be thrown. FQ may want to consider disabling this by default or providing site owners the option to disable per account or connection.

More at:
https://dev.mysql.com/doc/refman/5.7...-handling.html
https://dev.mysql.com/doc/refman/5.7..._full_group_by
and lots of Stack Overflow postings.

08-08-2018, 02:10 AM

Quote:

Originally Posted by Arthur

You can upgrade to PHP 5.6 (newer versions will be coming) by going into the CNC Control Panel, Server Info -> Change PHP version

Thanks.

One of my plugins is saying the best performance is with PHP 7.

I went in as suggested and saw that I was at 5.55.38 SSL version.

This was ticked on. Above that was PHP 5.6.29 Cannot find PHP 7. Also is it necessary to enable the 5.6.29 for MODULE/CGI/CLI?

I would have thought this was done by Fquest on the back end.

Respectfully

**Kevin** · 08-09-2018, 11:55 AM

We haven't gone to PHP 7 yet.

The Module in that context would be what your http site is using. You probably aren't using PHP via CGI at all but the CLI option is is what any cron jobs that call PHP scripts would use. I would suggest keeping them all the same version to avoid confusion unless you have a reason to downgrade one of them.

08-09-2018, 11:20 PM

Kevin, I am on https Does that make any difference?

I will go ahead and click on the latest PHP that you have suggested to avoid any conflicts.

Is there any idea when PHP 7 will be available here? HTTP/2, NGNIX etc.?

I was reading about HTTP/2 but I am not too sure if this speeds up HTTPS sites:

https://yoast.com/what-is-http2/

Respectfully

P.S. I notice when I log in to CNC via https, the Server Info says http://example.com and not https://example.com is that a cause for concern or should I open a ticket?

Quote:

Originally Posted by Kevin

We haven't gone to PHP 7 yet.

The Module in that context would be what your http site is using. You probably aren't using PHP via CGI at all but the CLI option is is what any cron jobs that call PHP scripts would use. I would suggest keeping them all the same version to avoid confusion unless you have a reason to downgrade one of them.

**Kevin** · 08-10-2018, 02:35 PM

The fact that you have https is why you have 4 things to set the PHP version of instead of 3. You can have your http and https sites running on different PHP versions if you want but as I said you shouldn't do that unless you have a specific reason to do so (like 2 apps that only work on different versions).

We don't have a time frame yet for PHP 7 or HTTP/2 and there has not been a decision to switch from Apache to NGINX.

As far as the server info page showing http that is simply what they all say. Every site has http but not every site has https so we show the one that will always work. Also, people who don't want to use http will still want to have it up to redirect visitors to the https site so that address will simply always work unless something is broken.

*skolnick* · 08-10-2018, 04:58 PM

Quote:

Originally Posted by Kevin

Before we can upgrade to MySQL 5.6 (from 5.5) we will have to force all the users who haven't yet to upgrade their password hash to the newer format as the old one isn't supported anymore. PHP 5.6 also requires this so that has been a big driving force in getting it done but there are still 39.2% of users on the old hash.

I'm one of the 39.2%. Linky to get my butt in gear and do the right thing please?