by writing the content now, clicking ‘publish’, editing the timestamp to a future time, and clicking ‘save’
Small correction to that sequence: Don’t click Publish until after you’ve updated the timestamp. You don’t want to run the risk of embarrassing premature-pingage, do you? 🙂
Traditionally, I would let FeedBurner do the pinging for me (as a free option) when it noticed new posts. However, since 2.2 (2.1?) I believe WP does now handle pinging on delayed posts.
Thread Starter
kybl
(@kybl)
Yes, sorry I typed too fast 🙂 publish should not be in there at all, correct? Just save – and then WordPress should do the ‘publishing’ and ‘pinging’ when the post becomes active.
Correct?
Thanks!
Close, but you do want to “Publish.” WP will notice the future date, no worries about that. If you just “Save”, it’ll remain a draft and not go out, regardless of the timestamp you assign.
Thread Starter
kybl
(@kybl)
ok – great. Then, to re-iterate, it will only PING when the post ‘goes live’, right? 🙂 Sorry to be dim, but I just want to be 100% sure.
Thanks again!
I’ve been researching this tonight. The Codex (until I just edited it) still indicated that the Pings (to the Update Services — NOT the outbound Pingbacks) all went out when you hit “Publish” as opposed to when the date in the timestamp arrives. I found a resolved bug in Trac that was fixed in 2.1, but after re-reading it, it appears that it was referring to outbound Pingbacks.
I’m now confused about this. Can anyone demonstrate conclusively that the Pings to the Update Services go out at one time or the other?
I don’t have a definitive answer, but I just noticed that my most recent 2 future posts was not pinging the services I have listed in my Options > Writing config. I had been using http://twitter.cross-poster.com/ – which does show new WordPress posts I make, if I publish now, but my posts do not show up on my twitter feed when it’s a future post.
DJ
