WP Toolkit shows wrong PHP version (using PHP Selector)
I am on a reseller hosting so I depend on the hosting provider when it comes to system configuration. I came from another hosting that has a very identical setup, so I know this must work actually.
In my WP Toolkit it shows me the wrong PHP version. I select the PHP version per cPanel account with the PHP Selector.
But in WP Toolkit it shows me some old PHP version.
While it does nothing to my system configuration, it's confusing and not supportive when updating PHP version on many accounts.
What could the hosting provider (or me) do to get this sorted out?
Someone else reported this already but never got a solution it seems:
https://support.cpanel.net/hc/en-us/community/posts/19164706552855-WP-Toolkit-fails-to-detect-correct-PHP-version-for-WordPress-websites
-
Can you confirm that under MultiPHP in WHM for this account that either inherit is selected (whereas PHP 7.2 is the default PHP version on the server) or ea-PHP 7.2 is set.
Andrew N. - cPanel Plesk VMWare Certified Professional
Do you need immediate assistance? 20 minutes response time!* Open a ticket
EmergencySupport - Professional Server Management and One-time Services0 -
I am not using the MultiPHP Manager but the PHP Selector. MultiPHP Manager is disabled via Featured List, which was the recommendation from my reseller hosting provider.
I temporarily enabled the MultiPHP Manager and I can obviously change PHP version there as well. So it's like I have two places where I can change the PHP version, but only one actually changes it?
Doing it this way, I am able to change the PHP version and it also shows in WP Toolkit.
However, I actually manage to break the site now, can't access it anymore.
So it seems there is the PHP Version maybe somewhere set globally at the server (7.2). And CloudLinux (I don't know it from a sys admin point of view as I am just using the reseller plan) allows to set a PHP version on a different level. And WP Toolkit reads out the global PHP version from the MultiPHP manager which is usually not enabled in my setup
"The system default PHP version is set by the system administrator. Any domain that is set to the inherit value indicates that it does not have its own PHP version explicitly set. Read more about inherit.
PHP 7.2 (ea-php72) Deprecation warning"
0 -
You shouldn't use MultiPHP Manager and PHP Selector together - additional details on that can be found here:
if that isn't what is happening in your case you'll need to work with the host to have them resolve the issue, or escalate to us if they think there is a problem with the server.
0 -
the host said already it's a bug with WP toolkit but I stopped believing what they say so I tried myself to test and research
it says in the link you provided "we strongly encourage you to set the MultiPHP Manager version to "inherit" if you wish to use PHP Selector" from what I remember and how I understood it (was not so easy for me) it's not set to inherit, it was just set to 7.2 (system or server php version)
Sidenote: I had another hosting provider where this issue did not show up, also using CloudLinux, to me as the user of the reseller account it looked very much like an identical setup, one solved it, the other one blaming cpanel
1 -
You wouldn't be able to set the version to inherit as that has to be performed on the parent side.
0 -
I see .. then I have anyway no other chance as dealing again with the reseller hosting company (or eventually just get my own licences and do all of it myself on a VPS). Thanks, I think I'll leave it at that now. I can also see in an overview all PHP versions in MainWP instead of WP Toolkit
1 -
I think this problem mostly occurs on accounts that have been migrated from another host, and the new host does not allow access to MultiPHP Manager.
I've done some breif investigation and if the host administrator can access MultiPHP and change the domain account setting (in MultiPHP) to "inherit", it will then follow the "PHP Selector" chosen PHP version persistently.
Ref: https://support.cpanel.net/hc/en-us/articles/360052492693-Using-the-MultiPHP-Manager-with-CloudLinux-s-PHP-SelectorHowever, we strongly encourage you to set the MultiPHP Manager version to "inherit" if you wish to use PHP Selector. This will ensure that the PHP Selector continues to be used even if the default version on the server changes.
Worth a try.
0 -
Worth a try.
I am not 100% sure anymore about the details, it was a huge pain and lots of back and forth with the hosting provider. I think the mentioned configuration did make a difference. The only thing I am not sure anymore if it worked also for new cPanel accounts or only those that were set up before applying that change
0 -
I just changed on a cPanel account via "PHP Selector" from PHP8.3 to PHP8.4. After that I checked what it shows on WP Toolkit. It shows still PHP8.3 and not the (inherited) PHP8.4
It's just bad.
Maybe it means I must temporarily enable Multi PHP Manager and mess around with it, or I must every time open a ticket with my hosting provider so they change something only to show the correct PHP version in WP Toolkit
0 -
UPDATE: My hosting uses "PHP Selector" only and the provider said they updated the account as follows (with reference to my previous post):
The solution here was to change the PHP management from MultiPHP to the CloudLinux Selector.
The incorrect account configuration was likely carried over from the cPanel migration/transfer.
Since fixing, I've found that WP ToolKit PHP version aligns with the "PHP Selector" and .htaccess is not overridden repeatedly with an "AddHandler..." alternate php version entry.
This CloudLinux related video looks helpful if you run your own WHM/Cpanel Server: https://www.youtube.com/watch?v=vGxDtY9fXSc&t=53s0 -
I didn't have time to look over your shared links CloudDaz but I checked the status today again of the cPanel account where I switched via PHP Selector from PHP8.3 to 8.4 → today it shows the updated version on WP Toolkit.
So perhaps it takes a few hours "to sync" and is not fully live information
0
Please sign in to leave a comment.
Comments
11 comments