Make WordPress Core

Opened 16 years ago

Closed 14 years ago

Last modified 14 years ago

#8737 closed enhancement (invalid)

Button to Publish Posts Scheduled for Later Immediately

Reported by: minusonebit's profile minusonebit Owned by:
Milestone: Priority: low
Severity: minor Version:
Component: Administration Keywords: needs-patch
Focuses: Cc:

Description

There have been several reports of posts scheduled not getting posted. I don't know the reason why and I have given up trying fixes and hacks. Its easier to just sign into console and edit the database directly.

Of course, there is the usual debate of whether its the WP application of the end user's server environment that causes the problem. I think its a WP problem, others are free to have their opinions.

Regardless of where the "blame" lies for the problem, the current implementation in 2.7 needs help.

As it is now, when a post misses its scheduled time, there is no way through the interface that I have found (you have to edit the DB) to get that post live because the "Publish Immediately" option goes away once you make it a scheduled post instead of a publish immediately post. You cant even convert it to a draft to publish it immediately. All you can do is edit the time that the post will be published (and putting in a new time X minutes from the present does not work, it simply misses those) so you actually have to copy and paste the post into a brand new post and publish immediately, or go through console.

And even if the posts missing the queue issue is fixed, this feature request should still be implemented. There should always be an option to take a post scheduled for later and make it live right now.

Change History (11)

#2 @Denis-de-Bernardy
16 years ago

  • Keywords reporter-feedback added; posts publish scheduled posts removed

Just FYI, every customer of mine who was complaining about future posts not getting published (or pings not happening, for that matter) turned out to have a HUGE ping list. And indeed, in this case, the cron job just... stopped on the ping list. Dropping the ping list to something more reasonable (one or two sites) fixed things up.

#3 @hailin
16 years ago

"Missed schedule" issues are fixed in:
http://trac.wordpress.org/ticket/8923

#4 @minusonebit
16 years ago

Does not look fixed in 8923 to me, it looks like they are still arguing about it. As I stated above, this feature request should be implemented regardless of if the bug is fixed now, later or never. There is no reason for posts scheduled for later publication to be trapped in that queue. The EU should always have an escape.

#5 @minusonebit
16 years ago

My ping list is ~15 sites and they all respond quickly. Who knows if that's it or not. You may be onto something, still poor implementation on WPs part if a slow ping site is enough to foil the entire process. It should be smart enough to time out and go to the next ping site on the list if a response is not forthcoming quick enough.

#6 @MichaelH
16 years ago

As reported by linusoft in the forums this plugin seems to overcome the problem:
http://blog.5ubliminal.com/posts/missed-schedule-future-posts-scheduled-mias-wordpress-plugin/

#8 @Denis-de-Bernardy
16 years ago

  • Keywords needs-patch added
  • Milestone changed from 2.8 to Future Release

punting...

#9 @Denis-de-Bernardy
15 years ago

  • Keywords reporter-feedback removed
  • Priority changed from normal to low
  • Severity changed from normal to minor

#10 @lloydbudd
14 years ago

  • Milestone Future Release deleted
  • Resolution set to invalid
  • Status changed from new to closed

Closing as invalid for now. Stale, and not enough technical info as to the factors.

Please create a new ticket with technical details if there is a high frequency or repro scenario.

#11 @RanYanivHartstein
14 years ago

  • Cc ran@… added
Note: See TracTickets for help on using tickets.