WordPress.org

Make WordPress Core

Opened 2 years ago

Last modified 13 months ago

#24160 new defect (bug)

ALTERNATE_WP_CRON runs wp_cron() too early

Reported by: r-a-y Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 3.4
Component: Cron API Keywords: has-patch 4.1-early
Focuses: Cc:

Description (last modified by SergeyBiryukov)

See #19818 for full details.

Then, read my comment in that ticket. Was advised to create a new ticket.

We need to run 'wp_cron' later than the default priority of 10 to allow plugins that run on this hook to properly initialize.

In the patch, I've bumped the priority to 99. Let me know what you think.

Attachments (1)

24160.01.patch (522 bytes) - added by r-a-y 2 years ago.

Download all attachments as: .zip

Change History (8)

@r-a-y2 years ago

comment:1 @SergeyBiryukov2 years ago

  • Milestone changed from Awaiting Review to 3.6

comment:2 @SergeyBiryukov2 years ago

  • Summary changed from ALTERNATE_WP_CRON runs 'init' too late to ALTERNATE_WP_CRON runs 'init' too early

comment:3 @SergeyBiryukov2 years ago

  • Summary changed from ALTERNATE_WP_CRON runs 'init' too early to ALTERNATE_WP_CRON runs wp_cron() too early

comment:4 @r-a-y2 years ago

Thanks for correcting the ticket title, Sergey!

And thanks for the feedback from the previous ticket.

comment:5 @prettyboymp2 years ago

To match where it runs with a normal cron, the hook should probably be changed to 'wp_loaded'.

comment:6 @ryan2 years ago

  • Milestone changed from 3.6 to Future Release

comment:7 @SergeyBiryukov13 months ago

  • Description modified (diff)
  • Keywords 4.1-early added
Note: See TracTickets for help on using tickets.