tollmanz / debug-bar-cron Goto Github PK

When a scheduled event does not fire and the associated timestamp is in the past, the human readable time still reports as positive.

DBC needs a console to report success/failure when running or deleting events, as well as for reporting general cron issues. This should be built with a true console (i.e., feedback on function execution) in mind that will come in later versions.

The recent update that shows missed events indicates that there may be an issue with cron in the installation. I would like to take this a bit further and try to actually diagnose the issue should one be present. I would need to research would exactly to check for, but this could be a very powerful debug feature.

It is very helpful in the debug process to be able to execute a cron callback function on demand. I envision a button next to each event that fires the function when clicked. Ideally, debug output would be generated as well. Experiments of this nature have begun in the develop branch.

WP core did it, and it's common practice. Let's do it.

I downloaded the version from the WordPress plugin repo and it worked fine
https://wordpress.org/plugins/debug-bar-cron/

I saw there were updates in the Github repo that were more recent than the plugins directory (latest commit 745ecbe) but when I downloaded and installed it caused the debug bar to stop working entirely. Both the WP plugin directory and the latest GitHub download were marked as v. 0.1.2

No PHP errors were visible, and I didn't see any JavaScript errors in the console either. No matter what page in the admin I was on clicking on the debug bar button or any of its sub-menu items would change the URL but nothing in the page's display would change.

Debug bar: v. 0.9
WordPress: v 4.9.2

Since post formats are a taxonomy, they should be supported as well.

There should be a simple means to removing events from cron. I think a simple button should do. The only trick is handling recurring events. Typical design patterns for scheduling recurring events will look to see if an event is scheduled and only schedule it if it is not scheduled. We need a good way to handle that scenario.

Missed this one.

There should be an easy way to unschedule crons that no longer have valid callback functions. This often occurs if a repeating event's callback function has a name change or is removed altogether.

Two of these have been missed:

• "update_network_counts"
• "wp_scheduled_auto_draft_delete"

There may be more.

The column showing the next execution time is a jumbled mess. The information is very important, so it would be nice to rework this to be a bit more readable.