| 开发者 | amglabs |
|---|---|
| 更新时间 | 2026年2月23日 23:43 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
amglabs-cron-inspector folder to /wp-content/plugins/Yes. AMG Labs Cron Inspector is read-only by design. It cannot modify or delete cron events. The only action it performs is manually triggering existing hooks, which requires admin capability and nonce verification.
A cron event is marked as overdue when its scheduled run time has passed but the event hasn't been executed yet. This can happen when:
DISABLE_WP_CRON is set to trueWhen DISABLE_WP_CRON is set to true in your wp-config.php, WordPress will not automatically run scheduled events on page loads. This is typically done when using a server-side cron job (recommended for high-traffic sites).
No. AMG Labs Cron Inspector is intentionally read-only to prevent accidental data loss. To delete cron events, use the WordPress function wp_unschedule_event() or a plugin designed for cron management.
Yes, but it only shows cron events for the current site. Network admins can view cron events on each site individually.