wordpress plugin wp missed schedule fix failed future posts with this problem and republish them correctly 10 items each session every 10 minutes .
available new beta version with code totally rewrited that applies innovative method for interval of check with lowest load server. This plugin patched an important unfixed bug since WordPress 2.5+ to date because Missed Schedule is a WordPress Bug!
All in One Gold Version with vary Frequency of Checking.
200.000+ Downloads and 60.000+ Active Installs! A special thank to all users who have installed this plugin: best regards by sLa NGjI's Team ;)
All previous versions, on fact, before the last stable, are deprecated and no longer supported in this project! We always recommend upgrading to the latest version!
Beta Version 2015.0228.3 Release 2015 Improved FREE:
Stable Version 2014.1231.2014 Release 2014 FREE:
All in One Gold Version with vary Frequency of Checking
Please noted that Special Gold Edition is dedicated to advanced users and was installed only on manual mode!
Development Version (code in becoming) Dev Preemptive FREE:
Alpha development release is available only on GitHub
Version 2013.1231.2015 Stable Release Reloaded 2013 FREE:
Please noted that on WordPress MultiSite, activation, and options panel is only available on Super Admin. Action Link Cron on left when plugin is activated is accessible only with WP Crontrol plugin Active.
Scheduled Posts Regression #22944 fixed on WP 3.5.1 is not related to this plugin.
Nothing is written into hosting space disk wp_option table auto cleaned when deactivate or deleted No need any other actions except activate or deactivate No need delete anything from hosting when deactivate No need delete anything from hosting when deleted No need delete anything from database when deactivate No need delete anything from database when deleted No need delete anything from wp_option when deactivate No need delete anything from wp_option when deleted
Branche is identified with first year on current version number (*2014*.1231.0) 2014 for example. Build is identified with progressive number on middle version number (2014.*1231*.0) 2014-12-31. Revision is identified with progressive number on last version number (2014.1231.*1*) 1 for example.