Skip to content

Knowledgebase

Selecting a website PHP version in Webuzo

control-panels, development

Use Webuzo MultiPHP Manager to select an installed PHP version for a particular domain. This lets applications use compatible runtimes without changing the default for every hosted website.

What you need before you begin

Check the application, theme and extension compatibility requirements and choose a PHP branch that receives appropriate security support. Record the current domain version and create a recoverable website and database backup. Only versions installed and allowed by the administrator are available.

01 Select a website PHP version in Webuzo

  1. Open the end-user panel and go to Configuration > MultiPHP Manager. Identify the exact domain and note whether it currently follows the default PHP version.
  2. Choose the supported version needed by the application from the domain dropdown and apply it. Change one test domain first if several sites share the account.
  3. Confirm required extensions are available for the selected version. A PHP version change does not necessarily give the new runtime every extension used by the old one.
  4. Test the site through the same HTTPS hostname visitors use. Check login, uploads and a database-backed operation, then inspect application and web-server errors.
  5. Review scheduled tasks separately. A cron command that names a specific PHP executable can continue using another runtime even after the website setting changes.
  6. When the site is stable, document the effective version and update future deployment requirements so an inherited default change does not surprise you.

What does Default PHP mean?

It follows the server default selected by the administrator. Choose an explicit compatible version when your deployment requires predictable per-domain behaviour, and review that choice during application upgrades.

Confirm the expected result

Confirm the application reports the expected PHP runtime through a protected diagnostic or its administrative system-information page. Remove any temporary public diagnostic file. Compare error logs with the pre-change baseline and test background work.

Troubleshoot unexpected results

If the application fails, return the domain to the recorded version while you investigate incompatibility or missing extensions. Do not keep an obsolete runtime indefinitely as the only remediation. If the desired version is absent, ask the server administrator to assess a supported installation rather than changing system PHP manually.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support

Powered by WHMCompleteSolution