[wp-trac] [WordPress Trac] #21072: CRON often returns ambiguous values
WordPress Trac
noreply at wordpress.org
Fri Feb 21 21:26:23 UTC 2014
#21072: CRON often returns ambiguous values
-------------------------+-----------------------------
Reporter: evansolomon | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Future Release
Component: Cron API | Version:
Severity: normal | Resolution:
Keywords: has-patch | Focuses:
-------------------------+-----------------------------
Changes (by nacin):
* milestone: Awaiting Review => Future Release
Comment:
I think this is good. While there are technically return value changes,
I'm not too concerned about the back compat.
wp_clear_scheduled_hook() probably just needs to return true (it got
cleared) or false, versus an array. It's also possible we change how that
function works in the future, #25773 gave us some trouble.
The wp_remote_post() call is non-blocking, so spawn_cron() should probably
not have a return value, right? Thus wp_cron() shouldn't have a return
value either. I know that was the original bug report — what about `true`?
Is that sufficient?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/21072#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list