Sponsors


Using WordPress datestamp for publishing a post in the future




I know more than a few people who write posts in bursts, writing 3-4 posts at one time altogether, and then do 2 options:
1. Either they will publish all the posts at one time, together; even though this may send these posts all at one time to their regular readers.
2. Or, they create these posts, save them, but do not publish them immediately. They log in later, from time to time, and publish these posts one by one.

Both of these options are not ideal; people like to be able to write their posts at any point of time, but get them published one by one at regular intervals. You can write these posts at any point of time, and control as to when these posts are actually published. WordPress gives you this facility right out of the box.
Suppose, you are running a photo tips blog on a WordPress platform, called http://5phototips.com/. You get up early in the morning, find that you have 2-3 hours to spare (and having nothing better to do at that point), write some 3-4 posts. You don’t want to release all of them at the same point, so you write them all in your blog post. Look at this screenshot for the WordPress post window.

Timestamp options on a WordPress Post Window

Now, click on the ‘Edit’ portion of the ‘Publish Immediately’ line just below the Publish Status caption. You get the following options available.

The publish timestamp options available at the WordPress Post Window
The publish timestamp options available at the WordPress Post Window

It is in this window that you can decide the timeframe at which you want the post to be published. You need to make sure that the post has been marked as ‘Published’, not just Saved. This puts it in a queue for publishing.




1 comment to Using WordPress datestamp for publishing a post in the future

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>