Test WordPress compatibility before changing PHP and keep a quick rollback path for a live site.
Applies to: WordPress on Tudor Internet Web Hosting
WordPress problems often come from the interaction between PHP, plugins, themes, caching, scheduled tasks and database state. Change one item at a time, record what you changed and keep a known-good backup before updates or repairs.
Before you start
- Sign in to the Customer Portal and open the affected hosting service.
- Take a current backup before changing website files, databases, DNS or application configuration.
Step-by-step
- Check the WordPress, theme and plugin requirements and remove unsupported components before the PHP change.
- Create a backup and reproduce the site on staging when it is commercially important.
- Enable WordPress and PHP logging without displaying errors publicly, then test the site on the target PHP version.
- Change PHP for the intended SiteWorx domain or application only; confirm whether the setting is per-domain or inherited.
- Test administration, public pages, forms, cron, image processing and any payment or API integration.
- Review new warnings and fatal errors and update or replace the component causing them.
- If production fails, revert to the recorded previous PHP version and investigate on staging.
Confirm the result
- The intended hostname loads over HTTPS from a private browser session and serves the correct website.
- Forms, database-driven pages and the administration area work without a new PHP, permission or redirect error.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| WordPress shows a critical error or blank page. | A plugin, theme, PHP version or exhausted resource caused a fatal error. | Check the PHP error log, disable only the last changed component and restore a known-good copy if the administration area is unavailable. |
| The site works until cache is cleared or a plugin updates. | Generated cache, stale object data or incompatible code is masking the underlying fault. | Test with caching disabled on a staging copy, update one component at a time and confirm PHP compatibility before re-enabling cache. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The affected domain and SiteWorx account
- The exact error text and time
- The last change made
- Relevant log lines with passwords and personal data removed
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Change the PHP version
- View website and error logs
- Diagnose a WordPress plugin or theme conflict
- Fix a 500 Internal Server Error
- Configure and clear WordPress caching safely
Last reviewed: 2026-07-18.
