Is Widget Logic still maintained?
No. The WordPress.org plugin team closed Widget Logic on 14 April 2026, 5 months ago, giving the reason as "Guideline Violation". The directory does not say which guideline. Either way the listing is gone, so WordPress cannot install it or deliver an update to a site that already has it.
The evidence
Every figure below is read from the WordPress.org plugin directory. Nothing here is our assessment of the code.
| Directory status | Closed by the plugin team, not available to install or update |
|---|---|
| Closed on | 14 April 2026 (5 months ago) |
| Reason given | “Guideline Violation” |
| Closure | Stated as permanent in the directory's notice |
| Read from the directory | 12 October 2026 |
Once a listing is closed the directory stops publishing its release date, tested-up-to version, install count and support figures, so the release details below come from the plugin's code archive instead.
What its code archive shows
| Last release | Version 6.9 (tagged 14 April 2026) |
|---|---|
| Tested up to | WordPress 6.9 |
| Requires | WordPress 3.0, PHP 5.4 |
| Releases in the archive | 41 |
| Read from | plugins.svn.wordpress.org/widget-logic, 12 October 2026 |
The directory keeps a closed plugin's code readable, and the last release tagged in Widget Logic's archive is version 6.9, tagged on 14 April 2026. That is within a month of the listing being closed: it was still being released, and the closure is what stopped the updates. A site still running it has a copy at least 5 months old.
That release declared itself tested up to WordPress 6.9, 2 releases behind the current WordPress 7.1.3. It asked for WordPress 3.0 and PHP 5.4 or later. The WordPress releases since then have run against code its author has not re-tested, and no fix can reach it through the directory.
The archive holds 41 tagged releases, the oldest still there tagged on 29 February 2008. Its last release described the plugin in one line as: “Widget Logic lets you control on which pages widgets appear using WP's conditional tags.” That is the job something else has to take over on any site still running it.
Tag dates, almost always the day a release shipped. The count is the tags left, not every release ever made.
What these signals mean
A closed plugin is not a quiet one. A quiet plugin is still listed, and its author could ship a fix tomorrow. A closed one gets no update however long you wait, and the dashboard shows no sign of that: a plugin with no update available looks exactly like one that is up to date.
A guideline closure is the plugin team acting, not the author. The directory's guidelines cover matters such as licensing, what a plugin may do without the site owner's consent, and how it may promote itself inside the dashboard. The published reason does not name the guideline, and we have not guessed at it.
The directory's closure notice says the closure is permanent, so the listing is not expected to return. The closure is recent, so a copy installed before it may still be the latest version the author ever released, but nothing newer can arrive through WordPress from here.
What to do about it
Treat the plugin as unsupported from the date it was closed. A guideline closure says nothing directly about whether the code works today, but it does mean nothing will be delivered to fix it when a PHP or WordPress upgrade changes something underneath it.
Do not start by deleting it. Find out what depends on it, back up the database as well as the files, and test the replacement on a staging copy first, because deleting a plugin can run an uninstall routine that drops its tables.
The directory stops publishing a closed plugin's category, so this page does not suggest alternatives. Any replacement has to do the job that Widget Logic's last release, version 6.9, describes above. That release was tested against WordPress 6.9; one worth moving to is tested against 7.1.3 and still listed in the directory.
Is a site you look after running Widget Logic?
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.
Related plugin checks
- Is Shortcodes Ultimate still maintained? Updated 25 September 2026, current against recent WordPress. Nothing of concern.
- Is Breadcrumb NavXT still maintained? Updated 29 August 2026, current against recent WordPress. Nothing of concern.
- Is Simple Custom CSS Plugin still maintained? Last release 19 months ago, according to the WordPress.org directory.
- Is Classic Editor still maintained? Updated 28 May 2026, current against recent WordPress. Nothing of concern.
- Is Classic Widgets still maintained? Released 8 December 2025, tested up to WordPress 6.9.10, 2 releases behind.
Questions
Why was Widget Logic removed from the WordPress plugin directory?
The directory gives the reason as "Guideline Violation", quoted as it appears. That means the WordPress.org plugin team closed it for breaching the directory's guidelines. The notice does not say which guideline, and we have not tried to work it out.
Will Widget Logic keep working if it is already installed?
Usually, for a while. Closing a listing removes the plugin from the directory; it does not reach into sites and switch anything off. What stops is updates, and they stopped on 14 April 2026: WordPress cannot offer an update for a plugin that is not listed, so the installed copy is frozen at whatever version it reached, which can be no later than 6.9, the last release in its archive. The dashboard gives no sign of that, because a plugin with no available update looks exactly like one that is up to date.
Could Widget Logic come back to the directory?
Not on the directory's own account: its closure notice says the closure is permanent. If the plugin carries on anywhere, it will be outside WordPress.org, and updates from there do not arrive through the normal dashboard route unless the author supplies their own updater.
Is Widget Logic 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 12 October 2026. We report maintenance signals only, and never claim a plugin is insecure. All plugins we cover.