Adds an in-place Edit action for changing a job's recurrence and next-run time.<\/p>","1.0.0":"
Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":3630182,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.2.0","1.2.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3630182,"resolution":"1","location":"assets","locale":"","width":1718,"height":871},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3630182,"resolution":"2","location":"assets","locale":"","width":1746,"height":622}},"screenshots":{"1":"The Cron Dashboard, listing every registered job with next run, recurrence, and average execution time.","2":"The Schedule Manager, for adding custom recurrence intervals and scheduling new events."}},"plugin_section":[],"plugin_tags":[4567,94,247,4685,4568],"plugin_category":[54,59],"plugin_contributors":[267285],"plugin_business_model":[],"class_list":["post-346971","plugin","type-plugin","status-publish","hentry","plugin_tags-cron","plugin_tags-debug","plugin_tags-performance","plugin_tags-scheduler","plugin_tags-wp-cron","plugin_category-security-and-spam-protection","plugin_category-utilities-and-tools","plugin_contributors-donaldmvaldez","plugin_committers-donaldmvaldez"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/dmvaldez-cron-auditor\/assets\/icon-256x256.png?rev=3630182","icon_2x":"https:\/\/ps.w.org\/dmvaldez-cron-auditor\/assets\/icon-256x256.png?rev=3630182","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/dmvaldez-cron-auditor\/assets\/screenshot-1.png?rev=3630182","caption":"The Cron Dashboard, listing every registered job with next run, recurrence, and average execution time."},{"src":"https:\/\/ps.w.org\/dmvaldez-cron-auditor\/assets\/screenshot-2.png?rev=3630182","caption":"The Schedule Manager, for adding custom recurrence intervals and scheduling new events."}],"raw_content":"\n
WP-Cron quietly runs dozens of scheduled tasks on every WordPress site \u2014 core updates, plugin maintenance, email queues \u2014 and most site owners have no visibility into what's actually registered, when it will next run, or how much it costs in execution time. DMValdez Cron Auditor<\/strong> puts all of that in one clean dashboard.<\/p>\n\n Cron Dashboard<\/strong>\n* Lists every registered cron job: hook name, arguments, next run date\/time, and recurrence\n* Search jobs by hook name\n* Sortable columns<\/p>\n\n Action Controls<\/strong>\n* Run any scheduled job immediately, on demand\n* Pause a hook so it stops firing without deleting its schedule\n* Resume a paused hook at any time\n* Edit a job's recurrence and next-run time in place, without losing its hook or arguments\n* Delete a single scheduled event\n* Bulk pause\/resume multiple jobs at once<\/p>\n\n Schedule Manager<\/strong>\n* Add custom recurrence intervals (e.g. \"Every 15 Minutes\") beyond WordPress's built-in hourly\/twicedaily\/daily\/weekly schedules\n* Schedule brand-new cron events (one-time or recurring) with custom arguments<\/p>\n\n Performance Impact<\/strong>\n* Measures real execution time for each cron hook, both from live WP-Cron ticks and manual \"Run Now\" triggers\n* Rolling average execution time per hook\n* Site-wide estimated cron impact summary<\/p>\n\n DMValdez Cron Auditor never deletes a job's underlying schedule when you pause it \u2014 pausing simply stops it from firing until you resume it, so nothing is lost.<\/p>\n\n A few Pro-only areas are visible (clearly marked, never functional in the free version) as a preview of what's coming:<\/p>\n\n The free plugin will always remain fully functional on its own \u2014 these are optional additions, not a crippled trial.<\/p>\n\n\n No. DMValdez Cron Auditor only reads and manages the cron jobs already registered by WordPress core, your theme, and your other plugins, unless you explicitly use the Schedule Manager to add a new one yourself.<\/p><\/dd>\n No. Pausing a hook stops it from executing on future WP-Cron ticks, but its underlying schedule is left completely intact. Resuming it immediately restores normal behavior with no need to re-create the schedule.<\/p><\/dd>\n Yes. DMValdez Cron Auditor reads from and writes to the same It can, if that plugin or theme depends on the job running on schedule. Use the pause\/delete controls the same way you would use any cron management tool: understand what a hook does before disabling it. Core WordPress maintenance hooks are safe to leave alone.<\/p><\/dd>\n No. All cron data, schedules, and performance stats stay in your WordPress database. Nothing is transmitted externally.<\/p><\/dd>\n No. Timing callbacks are only attached during actual WP-Cron execution (What's included in the free version<\/h4>\n\n
Pro (coming soon)<\/h4>\n\n
\n
\n
dmvaldez-cron-auditor<\/code> folder to \/wp-content\/plugins\/<\/code>, or install it directly through Plugins \u2192 Add New<\/strong> in your WordPress dashboard.<\/li>\n\n
Does this plugin create any new cron jobs on my site?<\/h3><\/dt>\n
What happens to a job when I pause it \u2014 is it deleted?<\/h3><\/dt>\n
Does this work if I've disabled WP-Cron and use a real system cron job instead?<\/h3><\/dt>\n
cron<\/code> option that WordPress itself uses, so it works identically whether WP-Cron fires on page loads or you trigger wp-cron.php<\/code> via a real system cron job.<\/p><\/dd>\nWill pausing or deleting a job break the plugin or theme that registered it?<\/h3><\/dt>\n
Does this plugin send any data outside my site?<\/h3><\/dt>\n
Does the performance profiler slow down my site?<\/h3><\/dt>\n
wp_doing_cron()<\/code>), never on regular front-end or admin page loads, and stats are stored with a small rolling window rather than an ever-growing log.<\/p><\/dd>\n\n<\/dl>\n\n\n1.2.1<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n