Plugin profile · observed daily since 02 Aug 2026
Scheduled Post Guardian
Active installs60+ rounded
Current authorMark Jaquith
Owner changesNone while we have been watching
Last release2.5 years ago 06 Feb 2024
Support— no recent threads
Releases on record8
Rating2.8 /5 · 9
Added to directory02 May 2014
Requires WP5.2
Requires PHP7.2
Version lag0.7 behind
Tested up toWP 6.4.10 WordPress is now on 7.1
PluginPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by Mark Jaquith throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
Full observed history, including every field transition
Committing accounts
Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.
| Account | Releases | First | Last |
|---|---|---|---|
| markjaquith | 8 | 02 May 2014 | 06 Feb 2024 |
This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Very early-stage: 60+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
2 downloads a day over the last 7 days, falling 50% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
08 Aug 2026peak 11/day08 Sep 2026
Install band fell to 60+ on 07 Sep 2026, from 70+. Both figures are rounded to one significant digit, so the size of the change is not knowable from them.
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug | 01 Sep | 02 Sep | 03 Sep | 04 Sep | 05 Sep | 06 Sep | 07 Sep | 08 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 11 | 0 | 0 | 0 | 11 | 0 | 0 | 0 | 11 | 0 | 0 | 0 |
| Active installs | 70+ | 70+ | 70+ | 70+ | 70+ | 70+ | 70+ | 70+ | 70+ | 70+ | 70+ | 70+ | 60+ | 60+ |
Unchanged throughout: ratings total (9) · version (1.1.4) · support threads (0) · threads resolved (0)
38 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Added to directory12 years ago 02 May 2014
Requires WP5.2
Requires PHP7.2
Version lag0.7 behind
Is anyone still maintaining this?
- No release in 945 days (2.6 years). The last was 06 Feb 2024.
- Declares compatibility only up to WordPress 6.4.10, while 7.1 is current. The author has not confirmed it runs on the last 7 releases.
- The same account maintains 28 other plugins; the most recent update to any of them was 28 May 2026.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.
- 02 Aug 20261 month agoInstall band moved to 70+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 20261 month agoFirst observed by PluginPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 30 Jul 202513 months agoDormancy threshold crossed540 days since the last release (2024-02-06). Dormancy is a maintenance observation, not a judgement about the owner.
- 06 Feb 20242.5 years agoVersion 1.1.4 released
- 26 Oct 20214.5 years agoVersion 1.1.3 releasedfrom the release logCommitted by markjaquith.
- 01 Sep 20215 years agoVersion 1.1.2 releasedfrom the release logCommitted by markjaquith.
- 02 Aug 20215 years agoVersion 1.1.1 releasedfrom the release logCommitted by markjaquith.
- 24 Jul 20215 years agoVersion 1.1.0 releasedfrom the release logCommitted by markjaquith.
- 23 Dec 20205.5 years agoVersion 1.0.2 releasedfrom the release logCommitted by markjaquith.
- 02 May 201412 years agoVersion 1.0 releasedfrom the release logCommitted by markjaquith.
- 02 May 201412 years agoVersion 1.0.1 releasedfrom the release logCommitted by markjaquith.
- 02 May 201412 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by Mark Jaquith for all 38 days we have observed it.
- It was last released 2.5 years ago (06 Feb 2024).
- Its author declares it tested up to WordPress 6.4.10; WordPress is now on 7.1.
- WordPress.org reports 60+ active installs.
- It carries 9 ratings, averaging 2.8 out of 5.
What we don’t know yet
- No forum threads were open in the two months we measure, so how responsive its support is cannot be said. One new thread starts answering that.
What can’t be known
- Whether the quiet is neglect or a finished plugin. That is the author’s intent, which no dataset records, and a stable plugin can need no changes for years.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Similar plugins
This plugin has not been updated in a long time. These carry the same tags and describe themselves in the same terms, so they are a starting point for a replacement, not a recommendation. Check them yourself.
Missed Scheduled Posts Publisher by WPBeginner
Are your scheduled posts missing their publication times? Missed Scheduled Posts Publisher effectively resolves the 'missed scheduled post' …
30,000+ installs4.9★ (59)updated 16 Mar 2026
Compare side by side MWW Scheduled Post Trigger
Publishes missed scheduled posts when WordPress Cron fails. Ideal for small to medium sites.
60,000+ installs4.4★ (27)updated 07 Aug 2026
Compare side by side WP Missed Schedule Posts
Auto publish future/scheduled posts missed by WordPress cron
10,000+ installs3.0★ (6)updated 20 Jul 2017
no release in over 18 months
Compare side by side Snack Missed Schedule
Uses separate recurring cron task to check for missed schedules.
200+ installs5.0★ (2)updated 08 Sep 2026
Compare side by side Scheduled Posts Showcase
Display your scheduled and future posts on the frontend without generating 404 links. Show visitors what's coming next.
20+ installs4.0★ (1)updated 18 Aug 2026
Compare side by side Advanced Cron Manager – debug & control
View, pause, remove, edit and add WP Cron events and schedules.
30,000+ installs4.7★ (38)updated 10 Mar 2026
Compare side by side Grouped from the tags each author chose for their own plugin, so the grouping is only as good as those tags.
Reach out about this record
Corrections, missing context, or anything else about Scheduled Post Guardian: a person reads every submission, and corrections get a reply within 5 business days.