Help for owners
Some plugins on my WordPress site are no longer updated
Short answer
A plugin nobody updates will not get security fixes and may break with a new WordPress or PHP version. WordPress.org can close plugins, and then they can no longer be downloaded from the directory. Make a backup, list your plugins, check each one's status, and plan replacements for the ones that matter. Do not delete plugins blindly.
Does this sound like your situation?
- A plugin shows a notice that it has not been tested with my WordPress version.
- A plugin was removed from the WordPress directory.
- The developer's website is gone or does not answer.
- A security warning names a plugin I use.
- I have plugins nobody remembers installing.
Why does this happen?
The author stopped updating it
Plugins are often made by one person or a small company. When they lose interest, there are no more fixes, even though the plugin keeps working for a time.
WordPress.org closed it
Plugins can be closed for guideline violations, security issues or at the author's request. Closed plugins can no longer be downloaded from the directory. A plugin may also be closed if its readme marks it as deprecated.
Confirmed by developer.wordpress.org
It was adopted or may be adopted
WordPress.org allows a plugin that is no longer developed to be adopted by someone else, who must fix it and make sure it is secure. An adoption request may not succeed, so you cannot count on a rescue.
Confirmed by developer.wordpress.org
Newer versions of WordPress or PHP break it
A plugin that still works today may fail after the next update of the site or server, and then the site shows errors or a blank page.
What can I do about it today?
- Take a full backup firstAsk your host or your developer for a backup of the files and the database before any plugin change. Keep a copy outside the hosting account.
- List every pluginIn the dashboard open the plugins list and copy the name and version of each plugin, including inactive ones.
- Check each one's pageLook at the plugin's page in the directory or on its maker's site: last update, whether it is closed and what its support says.
- Rank by importanceMark plugins that handle payments, forms, logins or security first. Those are the ones to deal with soon.
- Do not delete or update everything at onceChanging many plugins together can break the site and hide which one caused it. Do one at a time, on a copy of the site if possible.
When should I bring someone in?
- A plugin that handles payments or logins is abandoned.
- The site was already hacked or shows spam pages.
- A replacement plugin changes how your pages look or how the shop works.
How do I handle it?
- Audit the pluginsEach plugin is listed with its purpose, last update, status and what depends on it.
- Try a copy firstChanges are made on a copy of the site, so a failed swap never reaches visitors.
- Replace or removeA maintained alternative, a small piece of custom code, or no plugin at all if the feature is not used.
- Release with a way backThe live change is made after a backup, with a tested rollback and a check of the site, forms and checkout afterwards.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is an old plugin automatically unsafe?
Not automatically, but nobody will fix a new flaw. The risk is higher for plugins that handle logins, payments or user data.
Can I just keep using it?
For a while, perhaps. Treat it as a temporary state and set a date to replace it.
Can I get a closed plugin back?
Only the plugin team decides about reopening or adoption, and the result is not certain. Plan the replacement instead of waiting.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.