Build a non-production copy for updates and testing without exposing personal data or allowing it to send real customer messages.
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
- Create a current backup of the production files and database, then choose a staging subdomain or private hostname.
- Copy the files and database into separate staging locations; never point staging and production at the same database.
- Update site URLs using a serialisation-safe WordPress tool and verify wp-config.php references the staging database.
- Password-protect or otherwise restrict the staging site and discourage search indexing.
- Disable real payment gateways, scheduled customer messages, integrations and outbound email or route them to a safe test destination.
- Apply changes on staging, test the complete user journey and record the files, database migrations and settings that need promotion.
- Deploy through a controlled production change and do not overwrite newer production orders, form entries or user data with an old staging database.
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 staging copy of a website
- Create a backup before changing a website
- Diagnose a WordPress plugin or theme conflict
- Update WordPress core, plugins and themes safely
- Migrate WordPress manually between hosting accounts
Last reviewed: 2026-07-18.
