[wp-trac] [WordPress Trac] #39828: Multiple do_pings events shouldn't be scheduled
WordPress Trac
noreply at wordpress.org
Fri Feb 10 02:44:52 UTC 2017
#39828: Multiple do_pings events shouldn't be scheduled
------------------------------+-----------------------------
Reporter: ethitter | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Pings/Trackbacks | Version: 2.0.1
Severity: normal | Keywords:
Focuses: |
------------------------------+-----------------------------
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.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/39828>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list