Plugin profile · observed daily since 02 Aug 2026

Fixed HTML Toolbar

Active installs50+ rounded
Current authorWeb357
Owner changesChanged hands once
Last release15 days ago 23 Aug 2026
Support no recent threads
Releases on record7
Rating5.0 /5 · 5
Added to directory23 Apr 2019
Requires WP5.3
Requires PHP7.3
Version lag0 up to date
Tested up toWP 7.1 up to date

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 Web357 since 03 Sep 2026, when it last changed hands. 1 ownership change on record since daily tracking began on 02 Aug 2026.

We track the wordpress.org account behind each plugin. An owner renaming themselves is recorded as a rename, never as a transfer. How ownership changes are detected

03 Sep 2026
Custody change, one of 5 plugins

Yiannis Christodoulou → Web357. 5 plugins moved between the same two accounts between 02 Sep 2026 and 03 Sep 2026.

Plugins in the same group: count-cwp, easy-custom-code, login-as-user, web357-cookie-consent-manager

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.

AccountReleasesFirstLast
Yiannistaos717 Jul 201923 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.

Very early-stage: 50+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.

5 downloads a day over the last 7 days, falling 59% 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 47/day07 Sep 2026
5.0
out of 5
5 ratings
55100%
400%
300%
200%
100%

Install band fell to 50+ on 08 Aug 2026, from 60+. 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.

Field25 Aug26 Aug27 Aug28 Aug29 Aug30 Aug31 Aug01 Sep02 Sep03 Sep04 Sep05 Sep06 Sep07 Sep
Downloads that day1111012000111101100

Unchanged throughout: ratings total (5) · active installs (50+) · version (1.1.1) · 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 directory7 years ago 23 Apr 2019
Requires WP5.3
Requires PHP7.3
Version lagcurrent

Is anyone still maintaining this?

  • Last released 23 Aug 2026, 15 days ago.
  • Declares compatibility with WordPress 7.1, which is current.
  • The same account maintains 5 other plugins, 5 of which were 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.

  1. 03 Sep 20265 days ago
    Custody change, one of 5 pluginsYiannis Christodoulou → Web357. 5 plugins moved between the same two accounts between 02 Sep 2026 and 03 Sep 2026.
  2. 23 Aug 202616 days ago
    Version 1.1.1 released
  3. 02 Aug 20261 month ago
    Install band moved to 60+Bands are rounded to one significant digit, so the size of the change is not knowable.
  4. 02 Aug 20261 month ago
    First 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.
  5. 26 May 20263 months ago
    Version 1.1.0 released
  6. 25 May 20263 months ago
    Version 1.0.9 releasedfrom the release logCommitted by Yiannistaos.
  7. 11 Feb 20224.5 years ago
    Version 1.0.3 releasedfrom the release logCommitted by Yiannistaos.
  8. 09 Apr 20215 years ago
    Version 1.0.2 releasedfrom the release logCommitted by Yiannistaos.
  9. 17 Jul 20197 years ago
    Version 1.0.0 releasedfrom the release logCommitted by Yiannistaos.
  10. 17 Jul 20197 years ago
    Version 1.0.1 releasedfrom the release logCommitted by Yiannistaos.
  11. 23 Apr 20197 years ago
    Added 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

  • The wordpress.org account holding it changed once on 03 Sep 2026, to Web357.
  • 5 plugins moved between the same two accounts in the same window.
  • It was last released 15 days ago (23 Aug 2026).
  • Its author declares it tested up to WordPress 7.1, which is current.
  • WordPress.org reports 50+ active installs.
  • It carries 5 ratings, averaging 5.0 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 Fixed HTML Toolbar: a person reads every submission, and corrections get a reply within 5 business days.

The record is never silently edited, and your email is never published.