I am running WP 3.5 Multi-site. One of the sites is a blog where we post once per day, every single day of the year. The content is the same each year, so to save time we wanted to convert all the existing posts over to 2013 dates. I constructed a quick SQL command to add exactly 1 year to each post_date and post_date_gmt, and change the post_status to ‘future’.
In the wp-admin control panel, it looks like everything was fine. It shows 350+ scheduled posts, and when I look through them they all have the proper dates. However, once that day comes they are not being actually posted.
I have tried creating new posts in the future to see if it would post, and it did work. Comparing the database fields between the manually scheduled post that worked and the ones I did via the batch SQL command look identical.
See this screenshot: http://i.imgur.com/DuvFQ.jpg
Notice how there are posts from the past few days which never left “Scheduled”.
The only difference I saw is the guid column. Some of the old posts (which are now future posts) have my blog’s old URL (a sub-directory as opposed to a sub-domain). Could this have something to do with why they aren’t posting properly? I also was thinking the wp_post_meta table might have some left over things which could be messing with the postings. Does this sound plausible?
I guess the real question here is should I even have expected a manual DB change like this to work?
Any help would be appreciated. Thank you!
- The topic ‘Manual DB change of post_date/status for scheduling posts didn't work’ is closed to new replies.