The whole category in one page.
THE MOST IMPORTANT POINT ON OUR SERVERS
HTTP wp-cron is blocked fleet-wide.
WordPress needs the HTTP method disabled in wp-config.php and a real cron job in cPanel.
Without it, scheduled posts, updates, backups and WooCommerce actions silently stop.
WHAT SCHEDULE
Every fifteen minutes for most sites. Every five for an active shop.
WHAT GOES WRONG MOST
A wrong or relative path, so nothing runs Both the HTTP method and a cron job active Jobs not recreated after a migration Output filling the disk
FOR PATHS
Always absolute, from your home directory.
FOR OUTPUT
Keep it on while testing. Suppress it or log it afterwards.
A job running every fifteen minutes emails you ninety-six times a day.
HOW TO VERIFY
Schedule a post and see whether it publishes.
Check WooCommerce scheduled actions for a pending backlog.
WHAT TO MONITOR
That the effect happens, not that the job exists.
Cron failures are silent.
WHAT TO CHECK AFTER A COMPROMISE
The full job list. Attackers use cron for persistence.
