A PHP version change can improve compatibility and access to maintained releases. It does not replace updating the website’s plugins and dependencies.
Prepare before switching
Make a matching backup of files and database. Update a staging copy first and check the application vendor’s supported PHP versions. Record the current domain selection and custom INI values. Avoid experimenting directly on a payment or admissions system during peak use.
Apply and verify
- Search cPanel for MultiPHP Manager.
- Find the exact domain and check its document root. Other domains sharing that root may be affected.
- Select the domain, choose a supported installed version and apply it.
- Open a fresh browser session and confirm the effective version in the application’s system-information screen.
- Test public pages, admin login, forms, uploads and checkout. Review private error logs.
If the site breaks
Return to the recorded working version while investigating. A blank page may indicate an incompatible plugin, missing module or dependency requirement. Do not expose errors publicly; use logs or staging.
Inherit follows the server’s default or the host’s Selector integration. An explicit version pins the selected branch, but does not freeze security patch updates. Ask support which integration applies. Cron may still use a different CLI binary.
Official references
Reviewed 2026-10-22. Menus and availability depend on your hosting plan and server configuration.
