WP Toolkit fails to detect correct PHP version for WordPress websites
On my web server, the default PHP version is an old version because of some legacy pages.
As on my current setup I can not set different PHP versions for different domains (don't have "multiphp" feature), I use the following workaround:
In the root folder of a (WordPress) website, I insert the following code at the beginning of the `.htaccess` file:
SetHandler application/x-httpd-alt-php82___lsphp
This way every PHP file in that folder is handled with PHP v8.2 and everything works.
However, WP Toolkit is not detecting this workaround, so it simply shows the following error:
WP Toolkit has found WordPress files at the following path:
Path /home/user/path/to/example.com
However, it does not seem that this WordPress website is working. Try restoring the website from a backup or cleaning up the redundant files.
[error]FailedToExecuteWpCliCommand: exit status 1[/error] Your server is running PHP version [old_version] but WordPress 6.3 requires at least 7.0.0.
Also, on the Dashboard tab, in the Status column, the "PHP version" row shows the global PHP version, not the "overwritten" version.
-
Hey there! Can you try using the cPanel method to show that instead and see if that works better for you? This is what our .htaccess code looks like: # php -- BEGIN cPanel-generated handler, do not edit # Set the "ea-php81" package as the default "PHP" programming language. AddHandler application/x-httpd-ea-php81 .php .php8 .phtml # php -- END cPanel-generated handler, do not edit0 -
Hey cPRex, thanks for your reply! I've tried your suggestion (and modified the package to match my servers version). The PHP selection works indeed, but unfortunately WP Toolkit still can't recognise this overwrite. 0 -
Do you have root access to the server or just access to your cPanel? 0 -
I do have ssh/terminal access to the server if that helps, but don't have root permissions. 0 -
You would need root access to the system to get this resolved, so you'll need to reach out to your hosting provider or datacenter for more details on this. 0 -
All right, thanks again, will do. Are you sure this is not a bug / missing feature with cPanel + WP Toolkit but the result of a wrong server config? What should I tell them to do or change? 0 -
It could totally be an issue with the software, but without root access to the logs and to do some additional testing, I'm honestly not sure. 0 -
I see, thank you for all your help! I also guess this is something global. Last question: Can you please help me, what would be the best way to report this issue in an official way, so someone can take a look into this? 0 -
Once your host confirms the issue they would be able to submit a ticket with us directly to file the report. 0 -
I just got the confirmation from the host: "[...] the workaround method you need to use won't reflect as expected within the WP Toolkit. I suspected this to be the case and have conferred with our Advanced team, getting confirmation that this limitation is outside our control." Receiving this confirmation, as you suggested, I asked them to submit a ticket to you about this. Hope it will arrive to you soon. Thanks again for your help! 0 -
Let us know what you find here so we can all learn! 0 -
Today I got an update from my hosting provider. They were able to reproduce and verify the issue and as you suggested, they've reported this to the cPanel team with ticket #95109324. 0 -
Thanks for that - I see we are waiting for them to respond, but we are working on the ticket with them. 0 -
We have the same issue, if a solution is available, please share it. 0 -
@Duplika - could you submit a ticket? I don't see that much progress was made on the previous one that was submitted. 0 -
@cPRex - Do you have any updates on this? 0 -
There was never a reply from the host in that ticket, so we didn't get very far. They wouldn't allow us access to the system, we sent one reply asking for clarification how things were setup, and that was the entire ticket. 0 -
Thanks cPRex! Sad to hear, thought they would be more cooperative on this. Still hope maybe someone from cPanel could reproduce this and a fix will be released someday. 0
Please sign in to leave a comment.
Comments
18 comments