Find the component causing an error without disabling everything permanently or changing several variables at once.
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.
Work through these checks
- Record the exact error, URL and time, then check the PHP and application logs before changing WordPress.
- Create a current file and database backup and, where possible, reproduce the issue on a staging copy.
- Disable the most recently changed plugin first. When the administration area is unavailable, rename only that plugin directory through File Manager or FTP over TLS (FTPS).
- If the cause remains unclear, disable plugins in controlled groups, test after each group and narrow the fault to one component.
- Temporarily switch to a current default WordPress theme only after recording the active theme and preserving customisations.
- Check the affected component’s PHP and WordPress compatibility, update notes and known conflicts before reinstalling or replacing it.
- Restore the normal theme and known-good plugins, clear every application or proxy cache and test logged-in and logged-out sessions.
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
- View website and error logs
- Create a staging copy of a website
- Fix WordPress stuck in maintenance mode
- Fix a 500 Internal Server Error
- Change the PHP version for a WordPress site
Last reviewed: 2026-07-18.
