This post is really a test, but I’ll share the full problem and solution (assuming the test works), so it might help someone else out there as well. \ud83d\ude42<\/p>\n
The other day, for the first time ever, I noticed that a post of mine hit my RSS reader (Thunderbird) with a date of 11\/29\/1999.\u00a0 I was busy with other things and decided to come back to it. Of course, I didn’t…<\/p>\n
The next time I posted, the date was correct again. I (foolishly) assumed that the problem was transient (and possibly corrected). A few more good<\/em> posts, then yesterday, back-to-back bad posts. I realized exactly what was different between the good<\/em> posts and the bad<\/em> ones. At least procrastinating paid off this time. \ud83d\ude42<\/p>\n All of my good<\/em> posts were made with Windows Live Writer locally on my laptop and then saved to the server as a draft for continued editing. All of my bad<\/em> posts were started and finished directly in the web interface of WordPress 2.5.1.<\/p>\n This certainly wasn’t a native 2.5.1 problem, because I’ve been running 2.5.1 a lot longer than my first bad RSS pull and until reasonably recently, I posted 100% of the time through the web interface. I selected the last few rows from the wp_posts<\/em> table and spotted the problem instantly.<\/p>\n The post_date_gmt<\/strong> had the following value in my three bad<\/em> posts: 0000-00-00<\/strong>. A Google search revealed this forum thread<\/a> discussing the problem. Some people seemed to think it was related to the installation of XCache<\/a> (others thought that you also needed a separate plugin installed to provoke the problem). Since I recently installed XCache (as reported in my NginX post<\/a>), I was more than willing to believe that this was my problem. Of course, I didn’t see how it worked when Windows Live Writer was posting, but it was certainly possible that it took a different code path…<\/p>\n