Jayvee Fernandez recently wrote on The Blog Herald about WordPress and it’s problems with historical timestamps.
A friend on Plurk asked whether it is possible to use actual historical dates on your blog’s CMS (i.e. 4th of July 1776 for Independence Day). I did some digging and there are posts that address this question.
While this is a neat idea, setting the post date to reflect the time period a work was created (e.g. a photo taken in 1985), it introduces some problems.
- You won’t be able to schedule posts to be published at a later date. Setting the timestamp to a historical date will cause it to go live immediately.
- Posts with historical dates won’t necessarily be seen on the homepage when they are published. As WordPress (by default) orders posts by date, users would have to browse the archives to find the post. If you’re a master of custom queries, you might be able to remedy it in some way.
- I’ve always thought of the post timestamp being the date of publication, not the date of the content’s creation.