Replace unreliable visitor-triggered scheduling with a controlled cron job only when the site requires it.
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
- Review scheduled WordPress events with a trusted tool and identify overdue or excessively frequent tasks.
- Confirm that wp-cron.php is reachable internally and not blocked by a security rule, maintenance plugin or incorrect site URL.
- For low-traffic or timing-sensitive sites, create a SiteWorx cron job that invokes wp-cron.php at an appropriate interval such as every five or fifteen minutes.
- Disable visitor-triggered wp-cron in wp-config.php only after the real cron job has been tested successfully.
- Avoid one-minute schedules for ordinary plugins and make sure tasks cannot overlap indefinitely.
- Check logs, queue status and the expected application action after the first several scheduled runs.
- Remove obsolete plugin events when the associated plugin has been uninstalled and no data process depends on them.
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 cron job
- View website and error logs
- Resource limit errors and slow sites
- Troubleshoot delayed WordPress scheduled actions and queues
- Configure and clear WordPress caching safely
Last reviewed: 2026-07-18.
