Create a verified backup and record the current version. Check the application, theme and extension vendors’ supported versions and plan a short maintenance window if needed.

1. Open Hosting Features > Domains > PHP Options and select the pencil beside the intended domain.
2. Choose the supported target version from the available dropdown and save. The Domains Manage view reflects the same setting, so you do not need to change both screens.
3. For a subdomain, review its separate inheritance or explicit-version choice in the subdomain edit form.
4. Test the actual web runtime and important application functions, including login, forms, uploads and background processing.
5. Inspect logs for new errors and check scheduled command-line tasks separately. Remove temporary diagnostic files when finished.

The website should use the selected supported runtime and operate correctly. A successful homepage alone is insufficient for an application with payments, uploads or scheduled jobs.

If the required version is missing, the provider must make it available to the account. Do not install server packages through an unauthorised shell workaround. If compatibility fails, return to the recorded supported version while correcting the application.

Record the current PHP version and any account-specific options before selecting a replacement. Check the application's requirements, including important plugins or extensions, rather than choosing a version only because it is the newest option in the panel.

Use a staging copy when available. Test login, contact forms, image uploads, payment callbacks and scheduled tasks after the change. A working home page does not prove every code path is compatible.

Why does a scheduled command report another PHP version?

The website handler and a command-line PHP executable can be configured separately. Check the executable used by the scheduled task rather than assuming the panel's website selection changes every command automatically. Ask us for the supported path when it is not documented for your service.

If the site fails, preserve the error and restore the recorded version through the supported control while you investigate. Do not leave detailed errors visible to customers or publish a permanent diagnostic page. Send us the application name, previous and selected versions, and a redacted error excerpt. We can help identify a missing runtime capability without needing your database password.

Not necessarily. A cron command can call a specific executable independent of the website runtime. Verify the command’s actual version and configuration.

• Applying permitted PHP settings to one SiteWorx domain
• Controlling which file extensions SiteWorx treats as PHP
• Scheduling a SiteWorx cron task with useful output
• Adding a pointer domain in SiteWorx

• InterWorx: Change PHP Versions
• InterWorx: Add Edit Delete Subdomains