Skip to content

Add wp_schedule_bulk_events function for bulk event scheduling#9768

Open
urlund wants to merge 12 commits intoWordPress:trunkfrom
urlund:trunk
Open

Add wp_schedule_bulk_events function for bulk event scheduling#9768
urlund wants to merge 12 commits intoWordPress:trunkfrom
urlund:trunk

Conversation

@urlund
Copy link

@urlund urlund commented Sep 5, 2025

Introduces wp_schedule_bulk_events to allow scheduling multiple cron events at once. This function optimizes bulk scheduling by batching updates to the cron option and includes error handling for concurrent modifications.

Trac ticket: https://core.trac.wordpress.org/ticket/63938


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

Introduces wp_schedule_bulk_events to allow scheduling multiple cron events at once. This function optimizes bulk scheduling by batching updates to the cron option and includes error handling for concurrent modifications.
@github-actions
Copy link

github-actions bot commented Sep 5, 2025

Hi @urlund! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

Thank you,
The WordPress Project

@github-actions
Copy link

github-actions bot commented Sep 5, 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 urlund.

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

Reformatted the wp_schedule_bulk_events function to use consistent spacing and array initialization style, improving code readability and maintaining coding standards. No functional changes were made.
Standardizes function and closure formatting in wp_schedule_bulk_events for consistency. Also reorders a comparison to check the current cron option value against the original, improving code clarity.
Standardized spacing in anonymous function definitions and function calls within wp_schedule_bulk_events for better readability and consistency.
Cleaned up the default array parameter in get_option by removing an unnecessary space for consistency and code style.
Separated the assignment of $orig_value and $bulk_value to improve code clarity in wp_schedule_bulk_events. This change ensures $orig_value and $bulk_value are independently assigned, avoiding potential confusion.
Replaces the arrow function in array_reduce with an anonymous function for compatibility and clarity when checking if all arguments are arrays.
Improves readability by reformatting the array_reduce call in wp_schedule_bulk_events to use multi-line syntax.
Removed unnecessary whitespace after the opening parenthesis in the array_reduce call for improved code style consistency.
@github-actions
Copy link

github-actions bot commented Sep 5, 2025

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.

Updated error codes in wp_schedule_bulk_events to be more specific: 'wp_schedule_bulk_events_verify_failed' for verification failures and 'wp_schedule_bulk_events_update_failed' for update failures. This improves error clarity and debugging.
Added a check to ensure wp_schedule_single_event is only called if the event is not already scheduled. This prevents duplicate cron events from being created for the same hook and arguments.
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.

1 participant