Plugin profile · observed daily since 02 Aug 2026
Content Scheduler
Active installs200+ rounded
Current authorPaul Kaiser
Owner changesNone while we have been watching
Last release11 years ago 26 Dec 2014
Support— no recent threads
Releases on record14
Rating2.4 /5 · 8
Added to directory09 Dec 2010
Requires WP2.9
Requires PHPfalse
Version lag3.0 behind
Tested up toWP 4.1.0 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 Paul Kaiser 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 |
|---|---|---|---|
| freakingid | 14 | 29 Mar 2011 | 26 Dec 2014 |
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.
Small but established: 200+ active installs. Enough sites to show it works in the wild, too few for adoption to say much on its own.
3 downloads a day over the last 7 days, rising 100% 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 13/day28 Aug 2026
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 | 15 Aug | 16 Aug | 17 Aug | 18 Aug | 19 Aug | 20 Aug | 21 Aug | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 0 | 0 | 0 | 11 | 0 | 11 | 0 | 0 | 0 | 11 | 0 | 0 |
Unchanged throughout: ratings total (8) · active installs (200+) · version (2.0.5) · support threads (0) · threads resolved (0)
27 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 directory15 years ago 09 Dec 2010
Requires WP2.9
Requires PHPfalse
Version lag3.0 behind
Is anyone still maintaining this?
- No release in 4,264 days (11.7 years). The last was 26 Dec 2014.
- Declares compatibility only up to WordPress 4.1.0, while 7.1 is current. The author has not confirmed it runs on the last 30 releases.
- Paul Kaiser publishes no other plugin in the directory, so there is no wider activity to compare against.
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 202627 days 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.
- 18 Jun 201610 years agoDormancy threshold crossed540 days since the last release (2014-12-26). Dormancy is a maintenance observation, not a judgement about the owner.
- 26 Dec 201411 years agoVersion 2.0.5 released
- 23 Dec 201411 years agoVersion 2.0.4 releasedfrom the release logCommitted by freakingid.
- 19 Dec 201411 years agoVersion 2.0.1 releasedfrom the release logCommitted by freakingid.
- 19 Dec 201411 years agoVersion 2.0.2 releasedfrom the release logCommitted by freakingid.
- 19 Dec 201411 years agoVersion 2.0.3 releasedfrom the release logCommitted by freakingid.
- 18 Dec 201411 years agoVersion 2.0.0 releasedfrom the release logCommitted by freakingid.
- 02 May 201313 years agoVersion 1.0.0 releasedfrom the release logCommitted by freakingid.
- 30 Jul 201214 years agoVersion 0.9.9 releasedfrom the release logCommitted by freakingid.
- 23 Dec 201114 years agoVersion 0.9.8 releasedfrom the release logCommitted by freakingid.
- 09 Aug 201115 years agoVersion 0.9.6 releasedfrom the release logCommitted by freakingid.
- 09 Aug 201115 years agoVersion 0.9.7 releasedfrom the release logCommitted by freakingid.
- 08 Apr 201115 years agoVersion 0.9.5 releasedfrom the release logCommitted by freakingid.
- 31 Mar 201115 years agoVersion 0.9.4 releasedfrom the release logCommitted by freakingid.
- 29 Mar 201115 years ago1 earlier releasesfrom the release logBetween 29 Mar 2011 and 29 Mar 2011. Listed individually in the public release log rather than here.
- 09 Dec 201015 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 Paul Kaiser for all 27 days we have observed it.
- It was last released 11 years ago (26 Dec 2014).
- Its author declares it tested up to WordPress 4.1.0; WordPress is now on 7.1.
- WordPress.org reports 200+ active installs.
- It carries 8 ratings, averaging 2.4 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.
Expiring Posts
This plugin adds functionality to expire a post on a given date.
1,000+ installs3.5★ (2)updated 23 Jan 2022
no release in over 18 months
Compare side by side Expire Sticky Posts
A simple plugin that allows you to set an expiration date on posts. Once a post is expired, it will no longer be sticky.
1,000+ installs5.0★ (2)updated 20 Dec 2014
no release in over 18 months
Compare side by side Auto Prune Posts
Auto deletes expires (prunes) posts after a certain amount of time. On a per category basis (single category, or all at once.
1,000+ installs4.2★ (10)updated 11 Nov 2025
Compare side by side Auto Post Expire
Sets an expiration date for posts, auto moving them to draft after the set period.
1,000+ installs5.0★ (1)updated 20 Jun 2025
Compare side by side Simple Expires
Enable Posts and Pages to automatically expire and change at a certain time, and provide notification of expiration.
500+ installs5.0★ (2)updated 08 Aug 2011
no release in over 18 months
Compare side by side Auto Post Expiry Manager
Automatically expire posts and custom post types at a specific date and time. Works with all public post types and uses a lightweight cron scheduler.
100+ installsupdated 23 Jun 2025
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 Content Scheduler: a person reads every submission, and corrections get a reply within 5 business days.