Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Usually, not as an automatic ban—but never as a routine production install. “Untested with your version of WordPress” means the plugin’s directory metadata contains no current compatibility confirmation. It does not prove that the plugin will fail. Before installing, weigh its maintenance and support record, the damage a failure could cause, and whether you can test and roll back safely.
What “untested” actually means
WordPress labels plugins as either “Compatible with your version of WordPress” or “Untested with your version of WordPress.” The latter is a metadata warning, not a failed compatibility test.
WordPress documentation notes that a plugin not updated since the latest core release may be incompatible—or its compatibility may simply be unknown. The Developer Handbook displays a stronger notice when a plugin does not support the last three major WordPress releases: “This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.”
Free tools Windows power users keep installed
One-click scans. No signup required.
The label can also be stale. A developer can change the readme’s Tested up to: value without publishing new plugin code. That value should represent the newest WordPress version actually tested, must not exceed the active release or release candidate, and does not need to change for minor WordPress releases.
#1 Best Overall
How to decide whether the risk is acceptable
Do not judge the warning in isolation. Use these four tests:
| Decision factor | Lower-risk signal | Higher-risk signal |
|---|---|---|
| Evidence quality | Recent changelog, active support replies, current documentation and credible reports of use with your WordPress and PHP versions | No meaningful maintenance, unanswered support threads, outdated requirements or reports of failures |
| Blast radius | A narrowly scoped feature that can be disabled without affecting visitors | Authentication, payments, personal data, redirects, caching, site-wide layout or other core business workflows |
| Reversibility | Recent backup, staging or clone, simple deactivation and access to hosting files | No tested backup, no staging environment, or no way to recover if the dashboard fails |
| Urgency | A valuable feature with no maintained alternative and time to test properly | A cosmetic or nonessential feature that can wait for author confirmation or a maintained replacement |
A warning combined with missing maintenance or support evidence is materially more concerning than a warning by itself.
Rank #2
Check the plugin before activating it
- Read the changelog. Look for recent releases, fixes involving your WordPress version, PHP compatibility and the specific feature you need.
- Review support activity and documentation. Check whether the author answers current questions and whether users report successful operation on comparable WordPress, PHP, theme and plugin combinations.
- Confirm requirements. Compare the plugin’s stated minimum PHP and WordPress versions with the versions running on your site.
- Identify the failure cost. Decide what would happen if the plugin broke logins, checkout, forms, scheduled jobs, redirects, page rendering or stored data.
- Look for an alternative. If another actively maintained plugin provides the same essential function, uncertainty is harder to justify.
Test it without risking the live site
Use a staging site or a recent clone that matches production as closely as possible: the same WordPress release, PHP version, theme, configuration and important plugins. Testing only activation is insufficient.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Exercise the workflows that matter
- Complete the plugin’s primary task from the administrator and visitor sides.
- Check logged-in and logged-out behavior, mobile layouts and affected templates.
- Run forms, checkout, login, search, redirects, imports, exports or scheduled tasks that the plugin touches.
- Inspect browser errors, PHP error logs and WordPress debug output where available.
- Test interactions with caching, security, SEO and page-builder plugins rather than assuming isolation.
Leave the clone running long enough to cover scheduled jobs and ordinary site traffic patterns. If a critical workflow fails in staging, do not “try it anyway” on production.
Back up before activation or an update
Make a current, restorable backup before installing, activating or updating the plugin. WordPress advises administrators to keep a current backup because problems can occur during plugin updates.
Prefer a backup that includes both the database and files, and verify that you know how to restore it. A backup that has never been tested is not a complete rollback plan.
Keep a rollback path
Before production activation, know how to:
- Deactivate the plugin from the dashboard.
- Restore the database and files from your backup.
- Reach the site through hosting tools if the dashboard is unavailable.
- Rename or remove the plugin directory under
wp-content/plugins/using FTP or your host’s file manager when necessary.
After activation, monitor front-end pages, administrator access, forms, checkout or payment flows, scheduled jobs and error logs. If a critical function breaks, deactivate the plugin and restore the known-good state instead of changing several unrelated plugins at once.
When waiting is the safer choice
Wait for author confirmation, a newer release or a maintained alternative when any of these apply:
- The plugin handles authentication, payments, private data or another security-sensitive function.
- The site is business-critical and downtime or lost transactions would be expensive.
- Support reports show unresolved compatibility problems.
- The author has stopped responding or the project shows no meaningful maintenance.
- You cannot create and verify a backup or test a rollback.
Uncertainty is a poor trade when the cost of failure is high. A nonessential feature can usually wait; a security or revenue workflow should not depend on an unverified plugin.
Keep WordPress itself current
WordPress’ support policy officially covers only the latest major release. Older major branches may receive security fixes as a courtesy, but there is no guaranteed timetable and no long-term-support branch. Keep core current while evaluating each plugin separately; being on an older WordPress branch does not make an untested plugin safer.
The practical verdict
You can sometimes install an untested plugin, but only after independent evidence supports it and you have reduced the downside with staging, a current backup and a tested rollback. Treat the label as a prompt to investigate—not as proof of failure and not as permission to ignore compatibility. For plugins with a large blast radius, weak maintenance evidence or no recovery path, wait.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
