[wp-trac] [WordPress Trac] #24160: ALTERNATE_WP_CRON runs wp_cron() too early
WordPress Trac
noreply at wordpress.org
Mon Nov 23 23:13:21 UTC 2020
#24160: ALTERNATE_WP_CRON runs wp_cron() too early
-------------------------------------------+----------------------------
Reporter: r-a-y | Owner: peterwilsoncc
Type: defect (bug) | Status: assigned
Priority: normal | Milestone: 5.7
Component: Cron API | Version: 3.4
Severity: normal | Resolution:
Keywords: has-patch early needs-refresh | Focuses:
-------------------------------------------+----------------------------
Changes (by peterwilsoncc):
* keywords: has-patch early => has-patch early needs-refresh
* owner: (none) => peterwilsoncc
* status: reopened => assigned
* milestone: Future Release => 5.7
Comment:
Moving this on to the 5.7 milestone for an early look.
* I understand this will have a side-effect of fixing #20537 too
* It's a backward compatibility break to simply move the action from `10`
to a higher number. It's possible to maintain it by using `wp_cron` to
register an action to run later on `init`. Possible but ugly.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/24160#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list