Plugin profile · observed daily since 02 Aug 2026
Child Themify
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 J B 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 |
|---|---|---|---|
| JohnPBloch | 12 | 31 Dec 2012 | 30 Jan 2018 |
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: 6,000+ active installs. A real user base, well short of the ecosystem’s larger plugins.
9 downloads a day over the last 7 days, rising 16% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
Install band fell to 6,000+ on 21 Aug 2026, from 7,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 | 18 Aug | 19 Aug | 20 Aug | 21 Aug | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 12 | 11 | 0 | 12 | 0 | 11 | 11 | 0 | 11 | 22 | 0 | 11 | 11 |
| Active installs | 6,000+ | 7,000+ | 7,000+ | 6,000+ | 6,000+ | 6,000+ | 6,000+ | 6,000+ | 6,000+ | 6,000+ | 6,000+ | 6,000+ | 6,000+ | 6,000+ |
Unchanged throughout: ratings total (42) · version (2.0.1) · support threads (0) · threads resolved (0)
30 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 3,135 days (8.6 years). The last was 30 Jan 2018.
- Declares compatibility only up to WordPress 4.8.30, while 7.1 is current. The author has not confirmed it runs on the last 23 releases.
- The same account maintains 3 other plugins, and none has been updated in over a year, the most recent on 08 Mar 2016.
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.
- 19 Aug 202612 days agoInstall band moved to 7,000+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 18 Aug 202613 days agoInstall band moved to 6,000+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 13 Aug 202618 days agoInstall band moved to 7,000+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 12 Aug 202619 days agoInstall band moved to 6,000+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 202629 days agoInstall band moved to 7,000+Bands are rounded to one significant digit, so the size of the change is not knowable.
- 02 Aug 202629 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.
- 24 Jul 20197 years agoDormancy threshold crossed540 days since the last release (2018-01-30). Dormancy is a maintenance observation, not a judgement about the owner.
- 30 Jan 20188.5 years agoVersion 2.0.1 released
- 04 Oct 20178.5 years agoVersion 2.0.0 releasedfrom the release logCommitted by JohnPBloch.
- 11 Sep 20178.5 years agoVersion 2.0.0-beta1 releasedfrom the release logCommitted by JohnPBloch.
- 04 Jun 20179 years agoVersion 1.2.0 releasedfrom the release logCommitted by JohnPBloch.
- 02 Aug 201610 years agoVersion 1.1.2 releasedfrom the release logCommitted by JohnPBloch.
- 14 Sep 201510 years agoVersion 1.1.1 releasedfrom the release logCommitted by JohnPBloch.
- 20 Dec 201411 years agoVersion 1.1 releasedfrom the release logCommitted by JohnPBloch.
- 19 Dec 201411 years agoVersion 1.0.4 releasedfrom the release logCommitted by JohnPBloch.
- 15 Apr 201412 years agoVersion 1.0.3 releasedfrom the release logCommitted by JohnPBloch.
- 13 Jan 201412 years agoVersion 1.0.2 releasedfrom the release logCommitted by JohnPBloch.
- 18 Jan 201313 years agoVersion 1.0.1 releasedfrom the release logCommitted by JohnPBloch.
- 31 Dec 201213 years agoVersion 1.0 releasedfrom the release logCommitted by JohnPBloch.
- 31 Dec 201213 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 J B for all 30 days we have observed it.
- It was last released 8.5 years ago (30 Jan 2018).
- Its author declares it tested up to WordPress 4.8.30; WordPress is now on 7.1.
- WordPress.org reports 6,000+ active installs.
- It carries 42 ratings, averaging 4.2 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.
When using the Customizer is not enough - Create a child theme from your installed themes and customize styles, templates, functions and more.
Create your child theme with options. Customize it many options.
Warns you about outdated template files in your child theme and shows a diff view of the changes between parent and child theme template.
A WordPress plugin to create block themes.
Download any theme from your WordPress admin panel's Appearance page by just one click!
Hello+ is a free WordPress plugin designed to work seamlessly with Elementor’s Hello suite of themes.
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 Child Themify: a person reads every submission, and corrections get a reply within 5 business days.