Opened 19 years ago
Closed 17 years ago
#1577 closed defect (bug) (fixed)
New Hook: future_post
Reported by: | skippy | Owned by: | markjaquith |
---|---|---|---|
Milestone: | 2.1 | Priority: | low |
Severity: | normal | Version: | 1.5.2 |
Component: | General | Keywords: | bg|has-patch bg|dev-feedback bg|2nd-opinion |
Focuses: | Cc: |
Description
Future-dated posts should really get their own hook, for a variety of reasons.
The attached patches create a new action, 'future_post'. These patches prevent publish_post from being triggered on future-dated posts.
1.5.1.3 and 1.6 patches included.
Attachments (2)
Change History (11)
#4
@
19 years ago
publish_post should still be called either on the publish time, (if using psuedo-cron) or on the first pageview after the publish date. (This may be a problem for sites that get very little traffic.)
Note: See
TracTickets for help on using
tickets.
Can you think of anything that would break (plugins maybe?) if publish_post were not called for future-dated posts?
What are your thoughts on building pseudo-cron functionality into WP and having future-pings be handled internally?