default chroot PHP cli should use Plesk panel PHP version & settings
Currently when a user uses SSH to execute PHP cli commands, it does not reflect the settings chosen in Plesk panel (it seems to be the default OS vendor PHP). While other PHP versions are available in "/opt/plesk/php/..." the current solution is neither ideal nor transparent to the user (most of them don't even know this path).
I suggest that the default chrooted PHP command
-) should use the same version as chosen as in plesk panel
-) and should use ini settings (memorylimit, maxexecution_time) as chosen in plesk panel
Ideally this should even be possible on domain level, but at least on subscription level.
The changes implemented in the Plesk Obsidian 18.0.44 release https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18044 The console now works using a domain’s PHP version instead of the system PHP.
-- AA / PD
Am surprised this is still an issue, surely this is an easy fix?
Customers are often confused when they adjust the PHP version for a specific domain through the controlpanel, but use the server PHP version by default through CLI. Upon changing the PHP version in Plesk a .bash_profile entry could be created for that domein linking the desired PHP version to a PHP alias.
When creating a Scheduled Task type "Run a PHP script", an option should be available to use Domain's php.ini file instead of General PHP.ini.
Oliver Burkill commented
I agree we need this but dont agree that the same PHP ini file should be used. It'd commone to use a seperate ini for php-cli as you may be using it for background taks that need much longer timerouts and/or higher memory limits.
We need this! chrooted users cannot use the php version from the server.
Andy Bird commented