| 开发者 | codynaut |
|---|---|
| 更新时间 | 2026年9月1日 15:33 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp-cron.php, and it keeps working with DISABLE_WP_CRON set. Multisite-aware: each site gets its own table and settings, and sites created after network activation are set up automatically.
Free vs Pro
Everything above is free, on every site, with no caps — unlimited monitored jobs, full 30-day history, unlimited email alerts, and the reliability analytics.
Pro adds the alerting and integrations that teams need:
cronvitals folder to /wp-content/plugins/, or install it through the Plugins screen in WordPress.define( 'DISABLE_WP_CRON', true ); to wp-config.php and schedule a server cron to hit wp-cron.php. CronVitals works either way, but a system cron gives deterministic scheduling.No. Nothing runs on the front end. The monitoring adds two no-op hook callbacks per cron job during wp-cron.php requests, plus one scan every five minutes. Log writes are one row per cron run.
A cron manager lets you view, add, edit, and run events. CronVitals doesn't manage your events — it watches them over time, records every run, catches the PHP errors that kill them, and alerts you. They solve different problems and many sites run both.
Yes, and a real system cron gives you more accurate timing. CronVitals records runs however wp-cron.php is triggered, and the missed-job scan works either way.
Deactivating only unschedules the plugin's own events — your log history and settings stay, so reactivating picks up where it left off. Uninstalling drops the log table and deletes every option and transient it created.
No. The free plugin works fully on activation with no account, no API key, and no signup prompt — it runs in anonymous mode and contacts nothing. A license is only needed for the Pro features.
The free version sends nothing. Pro contacts Freemius to validate your license and deliver updates, and — only if you turn it on and supply a URL — sends a periodic ping to the external monitor you chose. Job names, logs, and error messages never leave your database.
Yes, with the Pro external heartbeat. Because the alert comes from an outside monitor that expects a regular ping from your site, it fires even when WordPress itself can't run.
WooCommerce runs most background work through Action Scheduler, which is a separate queue from WP-Cron. Pro monitors that queue, including stalled-queue detection. Free monitors the WP-Cron events WooCommerce registers.