√ WP Missed Schedule Fix Failed Future Posts Plugin

★★★ Find Missed Schedule Posts that Match this Problem, Every 1 Minute, and it Republish them Correctly Fixed, 10 Items per Session.


Description

WP Missed Schedule Fix Future Posts Failed Cron Job: find Scheduled that match this problem, and it republish them correctly. For not use too many resources, process 10 items per session, every 1 minute. All others will be solved on next sessions, until no longer exist: 10 failed future posts every minute, 600 failed future posts every hour, 1 session every minute, 60 sessions every hour.

This plugin not decrase server performaces, why it check only wp_schedule_single_event and wp_publish_post Behavior, to no waste resources, and not physical Cron Job!

The default 10 Failed Future Posts per session, was introduced for compatibility with default WordPress Items Feed Syndication.

This plugin is designed, on fact, for heavy use of Scheduled Future Posts and RSS Grabbing (as FeedWordPress or WP-O-Matic), but also work well with a simple WordPress Blog or for use as a CMS.

New WP Missed Schedule Features and Future Updates.

Actual Version:

1. √ Introducing (a New Idea of sLa) Check Key Tag Authenticity.
2. √ Added Support for WordPress 3.6+ Coming Soon Release.
3. √ Compatibility of W3 Total Cache and other Caching Plugins.
4. √ JetPack and others Social Publishing Plugins Transparency.
5. √ Interference Free with others Scheduled Cron Jobs a scale.
6. All in One Gold Versions with vary Frequencyes of Checking.
7. Introducing Check Plugin Authenticity Before Activation.
8. Preemptive Support WordPress 3.7+ ~ 3.8+ Future Releases.

Future Version:

1. Admin Dasboard Options Control Panel.
2. Admin or User Customization of all Plugin Options.
3. Manual change the User Level Permissions.
4. Manual change the Frequency of Checking.
5. Manual Scheduling the Number of Checking Sessions.
6. Enable or Disable Header and Footer Log.

In the Future Version 2013/2014 of this plugin, it will be introduced the New Admin Dasboard Options Control Panel to Optimize all of its Features!

Scheduled Posts Regression #22944 fixed on WP 3.5.1 is not related to this plugin.

The configuration of this plugin is Automattic! and not need other actions from the Administrator except installing, uninstall or delete it, but, for completely automatization, try on put it on /mu-plugin/ directoy, and also your activation is Automattic! starting from first installation.

No need to delete anything from hosting space when deactivate!
No need to delete anything from hosting space when deleted!
No need to delete anything from the database when deactivate!
No need to delete anything from the database when deleted!
No need to delete anything from the wp_option when deactivate!
No need to delete anything from the wp_option when deleted!
wp_option table is auto cleaned when deactivate or deleted!
Not need other actions except installing or uninstall it!

Full Compatible with WordPress Versions from 2.6+ to 3.5+ add Preemptive Support for Coming Soon 3.6+ and Future 3.7+ ~ 3.8+ Releases. Ready to Single, Network Multisite installations, and old WPMU 2.6+ to 2.9+ (latest is 2.9.2) Multi Users. Also it is possible to work on old versions from 2.1+ to 2.5+ (latest is 2.5.1) and legacy 2.0+ branch, but the result is not guaranted. Run on Shared, Dedicated, Cloud and VPS Hosting, with high and low resources. Work under GPLv2 or later License. Implement GNU style coding standard indentation.

Citations:

I think that this is a great plugin to have installed as every
now and then WordPress will inevitably miss a post schedule.

Kevin Muldoon

Since there was only a small code, I didn't install the pluging,
but used the code in my functions-file.

Martin Aleksander

This plugin is quite easy to get to work. Just install it
and you are all set. You won’t have to delete or add anything
to your code. This plugin takes care of it all.

Perta Max

Find More on sLaNGjI's Developer Page @ SoftPedia.com.

Author Website: slangji.wordpress.com - Author Repositories: github.com/sLaNGjI

Follow Me on LinkedIn - Twitter - Gravatar - FaceBook - Google+ - FriendFeed - RSS

Author URL sLa moved to sLaNGjI update bookmark!

single, event, array, unix, time, stamp, wordpress_wp_missed_schedule

Screenshots

Frequently Asked Questions (FAQ)

WP Missed Schedule Fix Failed Scheduled Future Posts Cron Jobs

WordPress comes with its own cron job that allows you to schedule your posts and events. However, in many situations, the WP-Cron is not working well and leads to posts missed their publication schedule and/or scheduled events not executed.

To understand why this happen, we need to know that the WP-Cron is not a real cron job. It is in fact a virtual cron that only works when a page is loaded. In short, when a page is requested on the frontend/backend, WordPress will first load WP-Cron, follow by the necessary page to display to your reader. The loaded WP-Cron will then check the database to see if there is any thing that needs to be done.

Reasons for WP-Cron to fail could be due to:

  1. DNS issue in the server.
  2. Plugins conflict
  3. Heavy load in the server which results in WP-Cron not executed fully
  4. WordPress bug
  5. Using of cache plugins that prevent the WP-Cron from loading
  6. And many other reasons

Publish a bunch of future posts noticed that they won't publish and when time comes to go live they just turn Missed Schedule. Took a look at the Wordpress code and noticed future posts get assigned a cronjob ($unix_time_stamp, 'publish_future_post', array($post_ID)) wp_schedule_single_event Why don't you just look at the database and publish all posts with future status and date in past? My plugin WP Missed Shcedule looks for posts with a date in the past that still have post_status=future. It will take each post_ID and publish wp_publish_post it.

How to Work?

This plugin will check every 1 minute, if there are posts that match the problem described. ('WPMS_DELAY' ,1) To not use too many resources, it fix for 10 items per session, one session every 1 minute. LIMIT 10 All others failed will be solved in future sessions, until no longer exist. When you activate this plugin the first 10 "Missed Scheduled Future Posts" are fixed immediately. All others are fixed the next batch. On some case (rare?) are also fixed live. If you have "Missed Scheduled Future Posts" after this plugin is activated, is not one error or bug: wait the next checking. If "Missed Scheduled Future Posts" persist, verify that WordPress installation is clean, or exist conflict with other plugins.

N.B. If have active others plugins with the same functions of "WP Missed Schedule" this is on conflict and not work. I suggest to delete or deactivate all others, clean related database options table, and use only "WP Missed Schedule". In the same way "WP Missed Schedule" could create conflicts with other plugins with the same functions. In this case, delete or disable it and only used the others.

Dealing with WordPress "Missed Schedule"

If you are scheduling blog posts in WordPress and seeing a "Missed Schedule" message, it's likely caused by an issue with your web server, or it is WordPress that is causing the problem of your blog posts not being posted as scheduled. This is an annoying problem. However, there is a very simple fix that is easy to do. The "Missed Schedule" problem seems to point to the web server and WordPress. The "time/date" comparison needs to match in order for your blog posts to get published as scheduled. If you are currently using the WordPress, blogging platform, you can easily fix the issue by modifying the wp-cron.php file which is located in the root folder. You simply open your notepad editor in Windows and search for the following line of code, which is located towards the bottom on the file wp-cron.php file.

This is the code you need to search for: update_option(’doing_cron’, 0);

This is the code you need to replace it with: //update_option(’doing_cron’, 0);

Next step is to save the wp-cron.php file and upload to your web server. However, make sure that you renamed the current "wp-cron.php" on the web server to "wp-cron.php-org", just in case there is an issue, and you need to resort back to the original file. The final step is to schedule another blog post and make sure that it processes correctly and that it gets published according to schedule. To manually run the cron, you'll need to type or paste the code below in your Internet browser URL without the brackets. "yourdomain.com/wp-cron.php" If things are working correctly, it should return a blank screen. Furthermore, this should update the time/date" comparison between your web server and WordPress.

The Missed Schedule Problem

The way WordPress handles scheduling is that whenever a page is loaded, either from your blog or in your admin control panel, the file wp-cron.php is loaded. At normal, if correctly configured, the server can talk to itself just fine and WordPress scheduling system will works perfectly. It’s only when you start doing strange and weird things like not having DNS setup properly or blocking loopback connections then it will cause you problems. It is possible that certain web hosts are not allowing WordPress cron jobs to run but for many that is not the issue as scheduled posting was working before upgrading to WordPress 2.7.

In WordPress 2.7, the cron job design, which is the core of the scheduling engine, is significantly changed as you can from both wp-cron.php and cron.php in /wp-includes/ folder. In WordPress 2.7 wp-cron.php, there are references to local-time and doing_cron option is set to zero. This is not exist in WordPress version 2.6.5. This might be the cause of the problem as it’s very likely that your web server time is off by a few seconds or minutes from the WordPress official time. And doing_cron argument is set to zero making it absolutely necessary that your web server and WordPress time to match with each other in order for the scheduled post to go through.

Solutioni #1

If you think that your web server settings is the cause of the problem, simply type this URL in your browser http://www.yourblog.com/wp-cron.php (replace yourblog with your actual domain name) to verify. If you see a blank screen, then your web server settings is ok. You can proceed to solution #2. If you see some error pages, then kindly check with your web hosting technical staff and ask for their help.

Solution #2

This is the solution to fix local-time and doing_cron option in wp-cron.php. If your programming is good enough, you are free to change the code and fix the issue yourselves. Remember to backup your WordPress before applying any change in production.

If you’re not familiar with programming, don’t worry, there is a simple solution.

  1. Download WordPress version 2.6.5 from WordPress repository.
  2. Extract both wp-cron.php and cron.php file from version 2.6.5.
  3. Backup your WordPress database.
  4. Rename both wp-cron.php and cron.php in your web server to other name.
  5. Upload both wp-cron.php and cron.php extracted from version 2.6.5 to your web server via FTP client.

Conclusion

I hope the fix working fine for you. WordPress should really look into this issue seriously and provide a fix or help to resolve the issue faced by many of the bloggers. If WordPress is not able to publish future post at predefined time, it should recheck it periodically for several time, says every 5/10/15 minutes, and publish the post as soon as possible.

Installation

For users of single WordPress 2.6+ (via FTP)

  1. Download WP Missed Schedule from wordpress.org plugin repository.
  2. Upload it into /wp-content/plugins/wp-missed-schedule/ via FTP.
  3. Activate WP Missed Schedule.

For users of single WordPress 2.7+ (manual)

  1. Download WP Missed Schedule from wordpress.org plugin repository.
  2. Upload it into your WordPress directly from Plugin Add Feature.
  3. It will create a directory /wp-content/plugins/wp-missed-schedule/
  4. Activate WP Missed Schedule.

For users of single WordPress 2.7+ (auto)

  1. Search WP Missed Schedule from Plugin Add Feature.
  2. Install it live directly from wordpress.org repository.
  3. It will create a directory /wp-content/plugins/wp-missed-schedule/
  4. Activate WP Missed Schedule.

For users of old WPMU 2.6+ or Network Multisite 3.0+ (manual)

  1. Put directly wp-missed-schedule.php into /wp-content/mu-plugins/
  2. Activation of WP Missed Schedule should be AutomaTTic since setup!

For all users of single, multisite and WPMU WordPress (trick)

  1. Download WP Missed Schedule from wordpress.org plugin repository.
  2. Make new directory /mu-plugins/ on /wp-content/ via FTP
  3. Upload wp-missed-schedule.php into /mu-plugins/ via FTP.
  4. Activation of WP Missed Schedule should be AutomaTTic since setup!

How to uninstall WP Missed Schedule

  1. Disable WP Missed Schedule from Menu Plugins of Control Panel.
  2. Delete WP Missed Schedule from Menu Plugins of Control Panel.

Troubleshooting

If all else fails and your site is broken remove directly via ftp on your host space /home/your-wp-install-dir/wp-content/plugins/wp-missed-schedule/ or /home/your-wp-install-dir/wp-content/mu-plugins/wp-missed-schedule.php

Changelog

Todo List

Actual Version:

  1. √ Checking: 5 Future Posts for 1 Minute (2013.0130.2222)
  2. √ Tiket #3786523 Strange Messages (2013.0130.2222)
  3. √ Add Full Support for WP 3.6+ Coming Soon Release (2013.0131.3333)
  4. √ Free Interference with others Scheduled Cron Jobs (2013.0131.3333)
  5. √ Transparency of JetPack and others Publishing Plugins (2013.0131.3333)
  6. √ Default WordPress Items Feed Syndication Support (2013.0131.3333)
  7. √ Realtime Checking: 10 Future Posts for 1 Minute (2013.0131.3333)
  8. √ Tiket #3712701 TimeZone Issues (2013.0131.3333)
  9. √ Compatibility of Third Party Caching Plugins (2013.0131.3333)
  10. √ Tiket #4163854 W3 Total Cache Conflict (2013.0131.3333)
  11. √ Check Key Tag Authenticity (2013.0131.3333)
  12. All in One Versions with vary Check Frequencyes (2013.0000.4444)
  13. Check Plugin Authenticity Before Activation (2013.0511.2233)
  14. Preemptive Support WP 3.7+ ~ 3.8+ Future Releases (2013.0511.2233)

Future Version:

  1. Admin Dasboard Options Control Panel (2013.0000.2014) No Date Set!
  2. Admin or User Customization of all Plugin Options (2013.0000.2014) No Date Set!
  3. Manual change the User Level Permissions (2013.0000.2014) No Date Set!
  4. Tiket #3740220 Change Frequency (2013.0000.2014) No Date Set!
  5. Manual Scheduling the Number of Checking Sessions (2013.0000.2014) No Date Set!
  6. Enable or Disable Header and Footer Log (2013.0000.2014) No Date Set!

Development Release

Version 2013 Build 0511-BUGFIX.2233-DEVELOPMENTAL

Warning Notice

WP Missed Schedule 2011.0920.2011 silently updated 2013-01-30.
Please: re-download and re-install as soon as possible! Enjoy.

Disclaimer

If the version 2013.0131.3333 does not work well, please
upgrade to version 2013.0130.2222 as soon as possible!

All previous versions, before the last stable, are
deprecated and no longer supported in this project.

We always recommend upgrading to the latest version,
or the one immediately preceding!

2013.0131.3333

  • Recommended Update [BUGFIX] Fixed Ticket #3712701 TimeZone Issues
    • Please update as soon as possible!
    • Full Compatible with WordPress 2.6+ to 3.5+
    • Full Support for WordPress 3.6+ Coming Soon Release.
    • NEW Transparency of JetPack and others Publishing Plugins.
    • BUGFIX Fixed Tiket #3712701 TimeZone Issues
    • ENHANCEMENT Compatibility of Third Party Caching Plugins.
    • BUGFIX Fixed Ticket #4163854 W3 Total Cache Conflict
    • ENHANCEMENT Default WordPress Items Feed Syndication Support.
    • UPDATE Checking 10 Posts for 1 Minute (previous 5 items) ('LIMIT' 10)
    • UPDATE checking interval every 1 minute (previous 5 minutes) ('WPMS_DELAY' ,1)
    • SECURITY Introducing (a New Idea of sLa) Check Key Tag Authenticity.
    • UPDATE Key Tag Checking Mechanism.
    • Work under GPLv2 or later License.
    • Implement GNU style coding standard indentation.
    • Meet detailed Plugin Guidelines quality requirements.
    • BUMP Version 2013 Build 0131 Revision 3333

2013.0130.2222

  • Recommended Update [BUGFIX] Fixed (unusual/infrequent) Ticket #3786523
    • Please update as soon as possible!
    • Full Compatible with WordPress 2.6+ to 3.5+
    • Preemptive Support for WordPress 3.6+ and 3.7+ ~ 3.8+ Future Releases.
    • BUGFIX Fixed Ticket #3786523 in Some Circumstances Hosting Configurations.
    • ENHANCEMENT Checking Interval Modified from 5 Minutes to 1 Minute.
    • UPDATE checking interval every 1 minute (previous 5 minutes) ('WPMS_DELAY' ,1)
    • SECURITY Introducing (a New Idea of sLa) Check Key Tag Authenticity.
    • Work under GPLv2 or later License.
    • Implement GNU style coding standard indentation.
    • Meet detailed Plugin Guidelines quality requirements.
    • BUMP Version 2013 Build 0130 Revision 2222

2013.0106.1111

  • Silent Update [STABLE] Try WP 3.5 Scheduled Posts Regression Ticket #22944
    • Please update as soon as possible!
    • Full Compatible with WordPress 2.6+ to 3.5+
    • Work under GPLv2 or later License.
    • Implement GNU style coding standard indentation.
    • Meet detailed Plugin Guidelines quality requirements.
    • BUMP Version 2013 Build 0106 Revision 1111

2011.0920.2011

  • Major Update [CERTIFIED] WP 2.6+ to 3.3+ Single and MultiSite Environment
    • Please update as soon as possible!
    • Full Compatible with WordPress 2.6+ to 3.3+
    • UPDATE Check every 15 minutes 'WPMS_DELAY',15
    • UPDATE Fix 10 items per session 'LIMIT' 10
    • Ready to Single and Network Multisite Environment
    • Work under GPLv2 or later License
    • BUMP Version 2011 Build 0920 Revision 2011

2011.0424.3333

  • Silent Update [MAINTENANCE] WP 3.1 and 3.1.1 Upgrade. Fixed slowness.
    • PLEASE Update as soon as possible!
    • UPGRADE Make it full compatible with WordPress 3.1 and 3.1.1 a.k.a 3.1+
    • NEW Replaced wp_future_post function with wpms_future_post
    • NEW Very realtime missed scheduled failed future posts recovery and fixing
    • EXPLAINED WP Missed Schedule fix one failed post in a minute: cool!
    • UPDATE Preemptive support for WordPress 3.1.2-alpha and 3.2-bleeding
    • UPDATE Now fix 5 items per session (previous 10) 'LIMIT' 0,5
    • FIXED Low resource hosting slowness when execute session task
    • IMPROVED Code cleanup and compress again for new faster loading
    • IMPROVED Functions redefinied for best timeline
    • BUMP Version 2011 Build 0424 Revision 3333

2011.0214.2222

  • Silent Update [MAINTENANCE] WP 3.0.5 and 3.1-RC4-17441 Upgrade.
    • Please update as soon as possible!
    • UPGRADE Make it full compatible with WordPress 3.0.5
    • FIXED Some Hosting Crash with Full Strict Security Rules (.htaccess)
    • UPDATE check every 5 minutes (previous 15 minutes) ('WPMS_DELAY' ,5)
    • UPDATE Preemptive support for WordPress 3.1-RC4-17441
    • Bump Version 2011 Build 0214 Revision 2222

2011.0107.1111

  • Major Update [CERTIFIED] WP 3.1-RC2-17229 Compatibility Upgrade.
    • Please update as soon as possible!
    • First 2011 Major Release (Zero Bug Certified) :)
    • UPDATE Preemptive support for WordPress 3.1-RC2-17229
    • Bump Version 2011 Build 0107 Revision 1111

2010.1231.2010

  • Major Update [STABLE] Full WP 3.0.4 and 3.1-RC1-17163 Zero Bugs Compatibility Upgrade.
    • Please update as soon as possible!
    • Fix Missed Scheduled Future Posts Cron Job.
    • ZERO-BUGS Full Last 2010 Major Release.
    • UPDATE Preemptive support for WordPress 3.1-RC1-17163
    • FIXED WordPress wp_schedule_single_event Function Behavior.
    • FIXED WordPress wp_publish_post Function Behavior.
    • Make it full compatible with WordPress 3.0.4
    • Plugin Memory Consumption (less of 1KB or no more)
    • Only 3KB of unique php plugin file.
    • Full Strict Security Rules Applied.
    • Fixed Execution Time.
    • Reduce Code Bloat.
    • Code Cleanup for faster loading.
    • Nothing is written into your space disk
    • wp_option database table is cleaned after uninstall
    • Work with single WordPress 2.6.x to 3.1.x and old MU.
    • Work with Shared and VPS Hosting.
    • Bump Version 2010 Build 1231 Revision 2010

2010.1226.0246

  • Silent Update [MAINTENANCE] WP 3.1-RC1 Compatibility Upgrade.
    • Please update as soon as possible!
    • UPDATE Preemptive support for WordPress 3.1-RC1
    • Bump Version 2010 Build 1226 Revision 0246

2010.1220.0048

  • Silent Update [MAINTENANCE] WP 3.1-beta2-16997 Compatibility Upgrade.
    • Please update as soon as possible!
    • UPDATE Preemptive support for WordPress 3.1-beta2-16997
    • Bump Version 2010 Build 1220 Revision 0048

2010.1211.0038

  • Silent Update [MAINTENANCE] WP 3.0.3 and 3.1-beta1-16732 Compatibility Upgrade.
    • Please update as soon as possible!
    • UPDATE Make it full compatible with WP 3.0.3
    • UPDATE Preemptive support for WordPress 3.1-beta1-16732
    • Bump Version 2010 Build 1211 Revision 0038

2010.1201.1918

  • Silent Update [MAINTENANCE] WP 3.0.2 and 3.1-beta1 Compatibility Upgrade.
    • Please update as soon as possible!
    • NEW Make it full compatible with WP 3.0.2
    • NEW Preemptive support for WordPress 3.1-beta1
    • NEW More Accurate Links on Plugin Control Panel Description
    • Bump Version 2010 Build 1201 Revision 1918

2010.0821.1539

  • Silent Update [BUGFIX] Reduced Bloat and Code Cleanup.
    • Please update as soon as possible!
    • Bump Version 2010 Build 0821 Revision 1539

2010.0816.2254

  • First Public Stable Release (full WP 3.0.1 compatible)
    • Fix Missed Scheduled Future Posts Cron Job
    • Make it full compatible with WP 3.0.1
    • Preemptive support for WordPress 3.1-alpha
    • Plugin Memory Consumption (less of 1KB or no more)
    • Only 3KB of unique php plugin file.
    • Full Strict Security Rules Applied.
    • Code Cleanup for faster loading.
    • Nothing is written into your space disk
    • wp_option database table is cleaned after uninstall
    • Bump Version 2010 Build 0816 Revision 2254

2009.1218.2009

  • Make it full compatible with WP 2.9 and WPMU
    • Preemptive support for WordPress 3.0-alpha
    • Fixed Execution Time
    • Bump Version 2009 Build 1218 Revision 2009

2008.1210.2008

  • Make it full compatible with WP 2.7 and WPMU
    • Preemptive support for WordPress 2.8-alpha
    • Reduce Code Bloat
    • Bump Version 2008 Build 1210 Revision 2008