Plugin profile · observed daily since 02 Aug 2026 · CLOSED
Secretary
Archival record
This plugin no longer returns data from the WordPress.org plugin API. The figures below are the last known-good observation, frozen on 14 Oct 2026. WordPress.org does not publish a reason when a plugin is closed, and none is inferred here.
Active installsfewer than 10 rounded
Current authorChrisBAshton
Owner changesNone while we have been watching
Last release4.5 years ago 29 Jan 2022
Support— no recent threads
Releases on record4
Rating— no ratings yet
Added to directory20 Jul 2017
Requires WPfalse
Requires PHPfalse
Version lag—
Tested up toWP 5.9.19 up to date
PluginsPedia 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 ChrisBAshton 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 |
|---|---|---|---|
| ChrisBAshton | 4 | 20 Jul 2017 | 29 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.
Very early-stage: fewer than 10 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, steady against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
11 Sep 2026peak 11/day14 Oct 2026
No ratings on record, so there is no sentiment to report.
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 | 01 Oct | 02 Oct | 03 Oct | 04 Oct | 05 Oct | 06 Oct | 07 Oct | 08 Oct | 09 Oct | 10 Oct | 11 Oct | 12 Oct | 13 Oct | 14 Oct |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 11 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 11 | 0 | 0 | 0 |
Unchanged throughout: ratings total (0) · active installs (0+) · version (1.0.3) · support threads (0) · threads resolved (0)
74 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 directory9 years ago 20 Jul 2017
Requires WPfalse
Requires PHPfalse
Version lag—
Is anyone still maintaining this?
- No release in 1,744 days (4.8 years). The last was 29 Jan 2022.
- Does not declare which WordPress version it has been tested against. A field the author sets themselves, so it is left blank rather than reported wrong.
- ChrisBAshton 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.
- 15 Oct 202624 days agoRemoved from the WordPress.org directoryThe plugin stopped returning data from the plugin API for three consecutive daily passes. WordPress.org does not publish a reason when a plugin is closed; none is asserted here. The last known-good snapshot is frozen below as the archival record.
- 02 Aug 20263 months agoFirst observed by PluginsPediaDaily 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.
- 23 Jul 20233 years agoDormancy threshold crossed540 days since the last release (2022-01-29). Dormancy is a maintenance observation, not a judgement about the owner.
- 29 Jan 20224.5 years agoVersion 1.0.3 released
- 29 Jan 20224.5 years agoVersion 1.0.2 releasedfrom the release logCommitted by ChrisBAshton.
- 20 Feb 20215.5 years agoVersion 1.0.1 releasedfrom the release logCommitted by ChrisBAshton.
- 20 Jul 20179 years agoVersion 1.0.0 releasedfrom the release logCommitted by ChrisBAshton.
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
- The plugin stopped returning data from the WordPress.org API on 14 Oct 2026.
- It has been held by ChrisBAshton for all 74 days we have observed it.
- It was last released 4.5 years ago (29 Jan 2022).
- Its author declares it tested up to WordPress 5.9.19, which is current.
- WordPress.org reports fewer than 10 active installs.
What we don’t know yet
- Nobody has rated it. The first rating that arrives shows up here.
- 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
- Why it was closed. WordPress.org publishes no reason when a plugin is removed, and does not publish one later.
- 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
Reach out about this record
Corrections, missing context, or anything else about Secretary: a person reads every submission, and corrections get a reply within 5 business days.