Plugin profile · observed daily since 02 Aug 2026
Shortcodes and extra features for Phlox theme
Active installs80,000+ rounded
Current authoraverta
Owner changesNone while we have been watching
Last release1 month ago 01 Aug 2026
Support0 / 1 resolved, last 2 months
Releases on record147
Rating2.1 /5 · 7
Added to directory30 Aug 2016
Requires WP5.0
Requires PHP7.0
Version lag0.1 behind
Tested up toWP 7.0.4 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 averta 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 |
|---|---|---|---|
| averta | 147 | 30 Aug 2016 | 01 Aug 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.
Widely adopted: 80,000+ active installs. Among the more broadly installed plugins in the directory.
481 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.
08 Aug 2026peak 2,734/day02 Sep 2026
Install band fell to 80,000+ on 19 Aug 2026, from 90,000+. 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 | 20 Aug | 21 Aug | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug | 01 Sep | 02 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 496 | 572 | 394 | 343 | 316 | 560 | 491 | 761 | 400 | 327 | 288 | 638 | 461 |
Unchanged throughout: ratings total (7) · active installs (80,000+) · version (2.17.22) · support threads (1) · threads resolved (0)
32 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 directory10 years ago 30 Aug 2016
Requires WP5.0
Requires PHP7.0
Version lag0.1 behind
Is anyone still maintaining this?
- Last released 01 Aug 2026, 32 days ago.
- Declares compatibility only up to WordPress 7.0.4, while 7.1 is current. The author has not confirmed it runs on the last 1 release.
- 0 of 1 support threads answered in the last two months.
- The same account maintains 4 other plugins, 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 20261 month agoInstall band moved to 90,000+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.
- 01 Aug 20261 month agoVersion 2.17.22 released
- 06 Jul 20262 months agoVersion 2.17.21 releasedfrom the release logCommitted by averta.
- 05 Jul 20262 months agoVersion 2.17.20 releasedfrom the release logCommitted by averta.
- 09 May 20264 months agoVersion 2.17.16 releasedfrom the release logCommitted by averta.
- 24 Jan 20267 months agoVersion 2.17.15 releasedfrom the release logCommitted by averta.
- 29 Dec 20258 months agoVersion 2.17.14 releasedfrom the release logCommitted by averta.
- 28 Dec 20258 months agoVersion 2.17.13 releasedfrom the release logCommitted by averta.
- 31 Aug 202512 months agoVersion 2.17.12 releasedfrom the release logCommitted by averta.
- 15 Jul 202514 months agoVersion 2.17.9 releasedfrom the release logCommitted by averta.
- 28 Jun 202514 months agoVersion 2.17.8 releasedfrom the release logCommitted by averta.
- 13 Apr 202517 months agoVersion 2.17.6 releasedfrom the release logCommitted by averta.
- 06 Mar 202518 months agoVersion 2.17.5 releasedfrom the release logCommitted by averta.
- 15 Feb 202519 months agoVersion 2.17.4 releasedfrom the release logCommitted by averta.
- 30 Aug 201610 years ago134 earlier releasesfrom the release logBetween 30 Aug 2016 and 08 Feb 2025. Listed individually in the public release log rather than here.
- 30 Aug 201610 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 averta for all 32 days we have observed it.
- It was last released 1 month ago (01 Aug 2026).
- Its author declares it tested up to WordPress 7.0.4; WordPress is now on 7.1.
- WordPress.org reports 80,000+ active installs.
- It carries 7 ratings, averaging 2.1 out of 5.
- 0 of 1 support threads in the last two months are marked resolved.
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 Shortcodes and extra features for Phlox theme: a person reads every submission, and corrections get a reply within 5 business days.