Plugin profile · observed daily since 02 Aug 2026
Hotfix
Active installs4,000+ rounded
Current authorMark Jaquith
Owner changesNone while we have been watching
Last release3 months ago 28 May 2026
Support— no recent threads
Releases on record14
Rating4.7 /5 · 18
Added to directory08 Feb 2011
Requires WP3.0
Requires PHPfalse
Version lag0.2 behind
Tested up toWP 6.9.7 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 | 7 | 08 Feb 2011 | 28 Dec 2011 |
| Otto42 | 1 | 12 Jul 2011 | 12 Jul 2011 |
| nacin | 3 | 07 Sep 2012 | 24 Jan 2013 |
| peterwilsoncc | 1 | 21 Feb 2019 | 21 Feb 2019 |
| jorbin | 2 | 12 Dec 2025 | 28 May 2026 |
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: 4,000+ active installs. A real user base, well short of the ecosystem’s larger plugins.
11 downloads a day over the last 7 days, falling 96% 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 1,554/day07 Sep 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 | 25 Aug | 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 11 | 1,554 | 498 | 11 | 11 | 11 | 11 | 11 | 12 | 11 | 11 | 11 |
Unchanged throughout: ratings total (18) · active installs (4,000+) · version (1.4) · support threads (0) · threads resolved (0)
37 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 08 Feb 2011
Requires WP3.0
Requires PHPfalse
Version lag0.2 behind
Is anyone still maintaining this?
- Last released 28 May 2026, 103 days ago.
- Declares compatibility only up to WordPress 6.9.7, while 7.1 is current. The author has not confirmed it runs on the last 2 releases.
- The same account maintains 28 other plugins; the most recent update to any of them was 04 Apr 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 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.
- 28 May 20263 months agoVersion 1.4 released
- 12 Dec 20259 months agoVersion 1.3 releasedfrom the release logCommitted by jorbin.
- 21 Feb 20197.5 years agoVersion 1.2 releasedfrom the release logCommitted by peterwilsoncc.
- 24 Jan 201313 years agoVersion 1.1 releasedfrom the release logCommitted by nacin.
- 11 Dec 201213 years agoVersion 1.0 releasedfrom the release logCommitted by nacin.
- 07 Sep 201214 years agoVersion 0.9 releasedfrom the release logCommitted by nacin.
- 28 Dec 201114 years agoVersion 0.8 releasedfrom the release logCommitted by markjaquith.
- 12 Jul 201115 years agoVersion 0.6 releasedfrom the release logCommitted by markjaquith.
- 12 Jul 201115 years agoVersion 0.7 releasedfrom the release logCommitted by Otto42.
- 26 May 201115 years agoVersion 0.5 releasedfrom the release logCommitted by markjaquith.
- 24 Feb 201115 years agoVersion 0.4 releasedfrom the release logCommitted by markjaquith.
- 08 Feb 201115 years agoVersion 0.1 releasedfrom the release logCommitted by markjaquith.
- 08 Feb 201115 years agoVersion 0.2 releasedfrom the release logCommitted by markjaquith.
- 08 Feb 201115 years ago1 earlier releasesfrom the release logBetween 08 Feb 2011 and 08 Feb 2011. Listed individually in the public release log rather than here.
- 08 Feb 201115 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 37 days we have observed it.
- It was last released 3 months ago (28 May 2026).
- Its author declares it tested up to WordPress 6.9.7; WordPress is now on 7.1.
- WordPress.org reports 4,000+ active installs.
- It carries 18 ratings, averaging 4.7 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.
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 Hotfix: a person reads every submission, and corrections get a reply within 5 business days.