-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Cron: Fix timestamp 0 handling across cron functions #9914
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: trunk
Are you sure you want to change the base?
Cron: Fix timestamp 0 handling across cron functions #9914
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN:
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
function wp_unschedule_event( $timestamp, $hook, $args = array(), $wp_error = false ) { | ||
// Make sure timestamp is a positive integer. | ||
if ( ! is_numeric( $timestamp ) || $timestamp <= 0 ) { | ||
if ( ! is_numeric( $timestamp ) || $timestamp < 0 ) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't be the same code block applied on wp_schedule_single_event() as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wp_schedule_event
+ wp_reschedule_event
too since all of them uses same validation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for catching this. I’ve updated wp_schedule_single_event
accordingly, and also applied the same changes to wp_schedule_event
and wp_reschedule_event
as they contained similar code.
function wp_unschedule_event( $timestamp, $hook, $args = array(), $wp_error = false ) { | ||
// Make sure timestamp is a positive integer. | ||
if ( ! is_numeric( $timestamp ) || $timestamp <= 0 ) { | ||
if ( ! is_numeric( $timestamp ) || $timestamp < 0 ) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wp_schedule_event
+ wp_reschedule_event
too since all of them uses same validation
Trac ticket: https://core.trac.wordpress.org/ticket/63987