Repository navigation
feat: schedule through Action Scheduler - #1
Merged
Merged
Conversation
ActionSchedulerDriver (own group, single and recurring events, the core's ten-minute duplicate window), a driver chosen by name or POLLORA_SCHEDULE_DRIVER that WordPress's scheduling functions follow through the pre_* filters, protected hooks, a buffer until Action Scheduler is ready, and WP-Cron for what it already holds or the driver cannot take.
This was referenced Oct 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Step 2 of the
pollora/schedulework: the Action Scheduler driver.ActionSchedulerDriver: own group, single and recurring events, the core's ten-minute duplicate window.Schedule::driver()/POLLORA_SCHEDULE_DRIVER/Schedule::extend(); WordPress's scheduling functions follow the driver through thepre_*filters (CronInterceptor).cronoption, protected hooks (action_scheduler_run_queue,protect(), filter) and an unavailable driver stay on WP-Cron; a new event goes to the driver.pre_get_scheduled_eventanswersnull, neverfalse, so the core still reads the option.action_scheduler_initare buffered and given once.ScheduleDriveris unchanged;DefersUntilReadyandFindsEventare optional.68 tests, PHPStan 0, Pint, lowest/stable. On pollora-test (develop + the framework PR, package linked), one
wp eval-fileprocess with Action Scheduler (WooCommerce) ready: the plugin patternif (! wp_next_scheduled()) wp_schedule_event()run twice leaves one action;wp_next_scheduled()andwp_get_scheduled_event()read it;wp_version_checkstays visible and is not duplicated; a duplicate single event answersduplicate_event;wp_clear_scheduled_hook()removes ours and leaves another plugin's action on the same hook; nothing is left behind and thecronoption is unchanged.