| 开发者 | jethalal |
|---|---|
| 更新时间 | 2026年9月27日 14:40 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/harvify-cron-monitor/No. It monitors and manages the existing WP-Cron system and, when present, Action Scheduler. It does not change how cron is triggered.
WordPress core does not expose a per-event start/finish hook, so WP-Cron timings are best-effort. Action Scheduler jobs are measured exactly.
No. It schedules hooks that already exist on your site and can make scheduled HTTP requests. It contains no code editor and no evaluator.
anonymous_mode option, so activation now shows Freemius's
standard opt-in screen. Nothing is sent before you answer it, and choosing Skip
leaves the free tier fully usable and still sends nothing.hcm_ prefix, which is shorter than WordPress.org accepts.
Functions, options, cron hooks and the plugin's own actions and filters are now
harvify_cron_*; global constants are HARVIFY_CRON_*; classes are
Harvify_Cron_*.harvify-cron/v1. The old hcm/v1
namespace is GONE and there is no compatibility alias — any code that calls
hcm/v1 routes will 404 until it is updated. Also renamed: the admin script and
style handle hcm-admin is now harvify-cron-admin, the localized JavaScript
object hcmAdmin is now harvifyCronAdmin, and the plugin's hooks are now
harvify_cron_run_recorded, harvify_cron_digest_frequency_changed and
harvify_cron_fs_loaded.Contributors field now names the correct WordPress.org account.admin-ui, so the package shipped in the download but was never loaded and
the control could not render -- which also meant the opt-in could never be switched on. Fixed by
loading the package. Your data was never at risk: with the control unreachable the plugin always
took the safe path and kept everything.