Use a backup, compatibility review and staged change sequence instead of pressing Update All on an untested production 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
- Read release notes and confirm that the current PHP and WordPress versions meet every critical plugin and theme requirement.
- Take a current file and database backup and verify that a restore point is available.
- Apply changes on staging first for business-critical, ecommerce or membership websites.
- Update WordPress core, then the active theme and plugins in small groups while testing after each group.
- Run any requested database upgrade once and do not interrupt extraction or migration processes.
- Clear application caches and test login, forms, search, checkout, scheduled tasks and integrations.
- If a fault appears, use the logs and the last changed component to roll back narrowly rather than restoring the entire site immediately.
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
- Create a backup before changing a website
- Create and use a WordPress staging site
- Diagnose a WordPress plugin or theme conflict
- Keep websites and extensions updated
- Recover a WordPress administrator password
Last reviewed: 2026-07-18.
