A PHP version change can make an application compatible with current dependencies and security updates. It can also reveal code that relied on an older runtime. Treat the change as a small deployment with a recorded starting point and a test plan.
IN THIS ARTICLE
Prepare for the change
Check the application, theme, plugin and encoded-software requirements. Prefer a release still supported by the PHP project. A version remaining visible in a hosting selector does not prove that upstream security support continues; separately supplied extended support has its own scope.
01 Change the setting
- In Plesk, select the correct subscription and open PHP Selector from the available sidebar or additional tools. This guide applies to Linux subscriptions where the CloudLinux integration is installed. Windows Plesk uses its own PHP configuration.
- Check the active PHP version and which websites the selector change will affect. Plesk also has a native PHP Settings page for each domain. A CloudLinux setting will not automatically override a different Plesk PHP handler. Confirm which handler serves the website first.
- Record the current version and whether the selector is using native. Note the enabled extensions and options because different PHP versions can have different settings.
- Choose a compatible supported version from Current PHP version and use Set as current or the save control shown by your interface. Change only the intended scope.
- Recheck required extensions and application limits for the selected version. Do not assume the previous version's extension selections were copied.
Confirm the expected result
Open the application's authenticated system information or health screen and confirm the web PHP version. Test sign-in, page editing, uploads, checkout where used, and scheduled work. An SSH command such as php -v can use a different CLI executable, so it is not sufficient proof of the website runtime.
What should I check if the PHP version change fails?
If the website fails, note the error and time, restore the recorded version while you investigate, and retest. Update incompatible application components in staging before trying again. If the version does not change, investigate the domain handler instead of adding conflicting .htaccess rules.