Make WordPress Core

Opened 9 years ago

Closed 7 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:


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. and 1.6 patches included.

Attachments (2)

execute-pings.patch (1.8 KB) - added by skippy 8 years ago.
functions-posts.patch (803 bytes) - added by skippy 8 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 matt9 years ago

  • Milestone changed from 1.5.2 to 1.6

comment:2 markjaquith9 years ago

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?

comment:3 matt9 years ago

I would like to see psuedo-cron built-in.

comment:4 duck11239 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.)

comment:5 markjaquith9 years ago

  • Owner changed from anonymous to markjaquith
  • Status changed from new to assigned
  • Version changed from to 1.5.2

skippy8 years ago

skippy8 years ago

comment:6 matt8 years ago

  • Priority changed from normal to low

comment:7 matt8 years ago

  • Milestone changed from 2.0 to 2.1

comment:8 ryan8 years ago

post_status = future fixes most of this.

comment:9 ryan7 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.