Is Classic Widgets still maintained?
Yes, going by its 8 December 2025 release. One thing lags: Classic Widgets declares compatibility up to 6.9.10, 2 releases short of the current WordPress 7.1.3. That means nobody has said it was checked against recent core, so check it yourself on staging before upgrading. It is not a sign that anything is broken.
The evidence
Every figure below is read from the WordPress.org plugin directory. Nothing here is our assessment of the code.
| Last release | 8 December 2025 (10 months ago) |
|---|---|
| Current version | 0.3 |
| Tested up to | WordPress 6.9.10 (current is 7.1.3, 2 releases ahead) |
| Requires PHP | 5.6 |
| Active installs | At least 2 million sites (the directory reports a rounded floor, not an exact count) |
| Support threads | 1 in the last two months, too few for the share resolved to mean much |
| Directory status | Listed |
| Read from the directory | 21 October 2026 |
Classic Widgets’s release history
| Listed in the directory since | 5 May 2021 |
|---|---|
| Tags in the archive | 3, the oldest left being 0.1 (5 May 2021) |
| Tagged in the year to 21 October 2026 | 1 |
| Read from | plugins.svn.wordpress.org/classic-widgets, counting tags up to 21 October 2026 to match the table above |
Classic Widgets's archive holds three tags up to 21 October 2026: 0.1 (5 May 2021), 0.2 (31 May 2021) and 0.3 (8 December 2025).
The longest stretch between two tags still in the archive is 4 years and 6 months, from 0.2 (31 May 2021) to 0.3 (8 December 2025).
Tag dates, almost always the day a release shipped. Authors can delete old tags, so the count is the tags left, not every release ever made.
What these signals mean
The "tested up to" field is the author telling you which WordPress version they last checked against. It goes stale on its own: WordPress ships roughly three times a year, so a field left alone falls behind whether or not the plugin itself has changed. A few releases behind usually means nobody has re-tested rather than that anything is broken.
The release date is the stronger signal, and here it is recent. The gap is worth knowing about because it moves the testing to you: before a major WordPress upgrade, nobody has said this plugin was checked against it.
What to do about it
Nothing to do today. This is a plugin to keep an eye on rather than one to replace.
What is worth doing is checking it again before your next major WordPress upgrade, and testing it on a staging copy rather than assuming. A tested-up-to version several releases behind is the author telling you they have not checked, which is exactly the thing staging exists to check for yourself.
Is a site you look after running Classic Widgets?
Our free WordPress plugin checker reads any public site and lists the plugins it loads, with the same maintenance signals as the table above for each one. No login and no signup, so it works on a client’s site before you have access to it.
Maintained alternatives
From the same category in the WordPress.org directory, filtered to plugins that have shipped a release in the last year and are installed on at least 10,000 sites. Chosen by those rules rather than by us, and worth checking against the same signals before you commit to one.
- Widget Options – Advanced Conditional Visibility for Gutenberg Blocks & Classic Widgets at least 100,000 sites, last updated 11 September 2026
- Custom Sidebars – Dynamic Sidebar Classic Widget Area Manager at least 100,000 sites, last updated 16 August 2026
- Classic Editor + at least 30,000 sites, last updated 14 October 2026
Related plugin checks
- Is Advanced Custom Fields still maintained? Updated 10 September 2026, current against recent WordPress. Nothing of concern.
- Is Custom Post Type UI still maintained? Updated 14 July 2026, current against recent WordPress. Nothing of concern.
- Is Yoast Duplicate Post still maintained? Updated 6 October 2026, current against recent WordPress. Nothing of concern.
- Is WPS Limit Login still maintained? Updated 18 September 2026, current against recent WordPress. Nothing of concern.
- Is Advanced Editor Tools still maintained? Updated 26 August 2026, current against recent WordPress. Nothing of concern.
Related links
- Which WordPress plugins are still maintained? Every plugin we check, with its last release.
- Custom WordPress plugin development When Classic Widgets has to be replaced or taken over and nothing in the directory fits.
Link to this check
Maintain Classic Widgets, or write about it? This badge links to this page, so your readers can see the same evidence. Copy the HTML below.
<a href="https://zignites.com/plugin-check/classic-widgets"><img src="https://zignites.com/badges/plugin-checker.svg" alt="Maintenance signals for Classic Widgets, checked with Zignites Plugin Checker" width="232" height="20"></a>Questions
What does "tested up to 6.9.10" actually mean?
It is the author's own statement of the most recent WordPress version they checked the plugin against. It is not a compatibility guarantee and it is not enforced by anything: WordPress ships roughly three times a year, so the field goes stale on its own unless somebody re-tests and updates it. A plugin several releases behind has usually not been re-tested rather than been found to break.
Is Classic Widgets still safe to install?
The directory shows a release on 8 December 2025, and nothing on this page is a security finding. What it does show is a tested-up-to version 2 releases behind current WordPress, so test it on a staging copy before a major WordPress upgrade rather than assuming it has been checked.
Is Classic Widgets a security risk?
We do not know, and nothing on this page is a security finding. Vulnerability data for WordPress plugins sits behind paid commercial APIs, and guessing at it from a version number either alarms people about plugins that are fine or implies that everything unflagged has been checked and is safe. Both are worse than saying nothing. What this page reports is maintenance: when the plugin last shipped, which WordPress version its author last tested against, and whether the directory still lists it. Those are facts the directory publishes, and they are what predicts whether a plugin will still work after the next core release.
Read from the WordPress.org plugin directory on 21 October 2026. We report maintenance signals only, and never claim a plugin is insecure. All plugins we cover.