WordPress has this wonderful feature that allows you to schedule posts to be automatically published at a specified time. This feature is a complete blessing for travel bloggers and bloggers who go on vacations. When you are in a different time zone, you don’t want to worry about getting up at odd hours to publish a post. You can simply relax and enjoy your vacation while WordPress schedule post feature do the work for you. It is all good until you realize that your entire publishing schedule was messed up, and none of your posts were published when you were away. If this has happened to you before, or you are someone who use the schedule post feature regularly, then you want to implement this trick to prevent the missing schedule error. In this article, we will show you how to fix the missed schedule post error in WordPress.
First thing you need to do is install and activate the WP Missed Schedule fix failed posts plugin. Thankfully, it is very easy to setup considering there are no settings to configure in the plugin.
The way how this plugin works is that it looks for posts that have missed their scheduled time. If WP Missed schedule finds a post that missed it’s schedule, then it will publish them correctly. To save resources on your server, it does this every 5 minutes and fixes 5 items in each cycle.
Recently some of our readers told us that schedule post feature is not working for them. Upon further research, we found that there are also some complaints about missing schedule posts and schedule post errors in the WordPress Trac. We found that it is actually an issue with WordPress 3.5. It is planned to be patched in the next security release 3.5.1.
You are probably wondering if this issue is new to WordPress 3.5, then how come the plugin has 37,000+ downloads? Well, the plugin has been around for some time now because this issue is not just with WordPress 3.5. It happens when your server configuration does not play nice with the default WP Cron. However, a group of folks are affected by this bug in WordPress 3.5 which should be fixed in version 3.5.1. For others having this issue, it is probably a web hosting issue.
Did you get affected by this issue? If so, then hopefully this solution fixed the problem. If you are still having the problem, or you found another fix, then please let us know in the comments below.