Skip to content

Conversation

@R1shabh-Gupta
Copy link

@R1shabh-Gupta R1shabh-Gupta marked this pull request as ready for review September 16, 2025 12:29
@github-actions
Copy link

github-actions bot commented Sep 16, 2025

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 props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props rishabhwp, rollybueno.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions
Copy link

Test using WordPress Playground

The 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

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

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 ) {

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?

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

Copy link
Author

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 ) {

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


// Manually add an event at timestamp 0 to the cron array.
$crons = _get_cron_array();
if ( ! $crons ) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

            if ( null === $crons ) {

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants