Opened 8 years ago
Closed 8 years ago
#39828 closed defect (bug) (fixed)
Multiple do_pings events shouldn't be scheduled
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 4.8 | Priority: | normal |
Severity: | normal | Version: | 2.0.1 |
Component: | Pings/Trackbacks | Keywords: | |
Focuses: | Cc: |
Description
Whenever _publish_post_hook()
is called, a new do_pings
event is scheduled in wp-cron. Since do_all_pings()
(the callback hooked to do_pings
by default) takes no arguments, and pings everything that needs pinging each time it runs, there's no need to schedule multiple of these events.
The potential for duplicate events has existed since its introduction in r3663. As part of #6966, r9181 aimed to reduce duplicate events. If a site's cron is backlogged, however, that workaround will fail as it only looks ahead.
Attachments (1)
Change History (3)
Note: See
TracTickets for help on using
tickets.
Only schedule an event if one doesn't exist