Plugin profile · observed daily since 02 Aug 2026
Expiring Posts
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 Ivan 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 |
|---|---|---|---|
| ivankk | 3 | 21 Mar 2019 | 23 Jan 2022 |
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.
Moderately adopted: 1,000+ active installs. A real user base, well short of the ecosystem’s larger plugins.
5 downloads a day over the last 7 days, steady against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
Install band rose to 1,000+ on 20 Aug 2026, from 900+. 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 | 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 | 11 | 11 | 0 | 0 | 11 | 0 | 14 | 0 |
| Active installs | 900+ | 900+ | 900+ | 900+ | 900+ | 1,000+ | 1,000+ | 1,000+ | 1,000+ | 1,000+ | 1,000+ | 1,000+ | 1,000+ | 1,000+ |
Unchanged throughout: ratings total (2) · version (1.3) · 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.
Is anyone still maintaining this?
- No release in 1,678 days (4.6 years). The last was 23 Jan 2022.
- Declares compatibility only up to WordPress 5.9.16, while 7.1 is current. The author has not confirmed it runs on the last 12 releases.
- The same account maintains 1 other plugin, 1 of which was updated in the last 90 days. the account is active.
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 202626 days agoInstall band moved to 900+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 202626 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.
- 17 Jul 20233 years agoDormancy threshold crossed540 days since the last release (2022-01-23). Dormancy is a maintenance observation, not a judgement about the owner.
- 23 Jan 20224.5 years agoVersion 1.3 released
- 21 Mar 20197 years agoVersion 1.1 releasedfrom the release logCommitted by ivankk.
- 21 Mar 20197 years agoVersion 1.2 releasedfrom the release logCommitted by ivankk.
- 21 Mar 20197 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 Ivan for all 27 days we have observed it.
- It was last released 4.5 years ago (23 Jan 2022).
- Its author declares it tested up to WordPress 5.9.16; WordPress is now on 7.1.
- WordPress.org reports 1,000+ active installs.
- It carries 2 ratings, averaging 3.5 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.
Auto deletes expires (prunes) posts after a certain amount of time. On a per category basis (single category, or all at once.
Sets an expiration date for posts, auto moving them to draft after the set period.
Enable Posts and Pages to automatically expire and change at a certain time, and provide notification of expiration.
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.
Schedule content to automatically expire and change at a certain time, and notify people of expiration.
This is the fork of Simple Expires created by Mr. abmcr. Simple plugin which can set up the term of validity.
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 Expiring Posts: a person reads every submission, and corrections get a reply within 5 business days.