A newer supported PHP release can improve security and application support, but compatibility must be checked before switching a production website. The version selected for one domain may differ from the server default or from the version used by a scheduled command. Record the current setup before you change it.
Recommended steps
- Check the requirements of your application, theme and plugins. Review required PHP extensions and limits as well as the version number. Update incompatible components before changing the production runtime.
- Take a current file and database backup. Where available, test the change on a staging copy that resembles the live application. Include less frequently used features such as imports, reports and background jobs.
- On a cPanel service with MultiPHP Manager enabled, select the intended domain and an available supported version. Do not assume that changing a parent domain also updates every separate website or custom command.
- Test login, forms, media processing and checkout after the switch. Review the error log for new exceptions, missing extensions and deprecated code. Keep a note of the exact change time for comparison.
- If an important feature fails, return to the previous supported configuration while you investigate. Check cron commands separately with Support if they use a different PHP executable or an explicit version path.
Do not publish a diagnostic phpinfo page containing your environment details. If you temporarily create a test file for verification, remove it immediately afterward. Ask Support which versions and extensions your plan makes available before relying on an unavailable runtime.
