Ticket #1577 (closed defect (bug): fixed)

Opened 7 years ago

Last modified 5 years ago

New Hook: future_post

Reported by: skippy Owned by: markjaquith
Priority: low Milestone: 2.1
Component: General Version: 1.5.2
Severity: normal Keywords: bg|has-patch bg|dev-feedback bg|2nd-opinion
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

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

Change History

comment:1   matt7 years ago

  • Milestone changed from 1.5.2 to 1.6

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   matt6 years ago

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

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.)

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

skippy6 years ago

skippy6 years ago

comment:6   matt6 years ago

  • Priority changed from normal to low

comment:7   matt6 years ago

  • Milestone changed from 2.0 to 2.1

comment:8   ryan6 years ago

post_status = future fixes most of this.

comment:9   ryan5 years ago

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