You have been told to keep your WordPress plugins updated.
Then you open an update and see a warning that the plugin has not been tested with the version of WordPress you are running.
Well, that is not particularly reassuring, is it?
Do you update it anyway? Wait until the message changes? Or leave it alone because everything seems to be working?
This is a fair question. Especially if you already feel nervous about making changes to your website.
The first thing to know is that not tested does not automatically mean it will break your website.
However, it is a reason to check a little further before deciding what to do.
Let’s walk through what to check when a WordPress plugin is not tested with your version.
What does the plugin compatibility message actually mean?
Plugins listed in the WordPress.org directory include a Tested up to value.
This tells you the highest WordPress release series the developer reports having tested the plugin against. WordPress explains the field in its plugin readme documentation.
If your website runs a newer release series, you may see a message saying the plugin has not been tested with your version.
That message does not tell you that testing failed.
It tells you that the published testing information does not confirm compatibility with your WordPress version.
There is a difference.
The plugin might work perfectly well, or there could be a problem. The label alone cannot answer that for your particular website.
First, check whether the plugin is being looked after
Open the plugin details in your dashboard or visit its official website.
Have a look at:
- When it was last updated.
- What the latest update changes.
- Whether the developer is answering support questions.
- Whether there are reports of problems with your WordPress version.
- Whether the developer has published any compatibility advice.
You are looking for the overall picture.
An older testing label alongside recent updates and helpful support is a different situation from an older label on a plugin with unresolved problems and no sign of maintenance.
The developer can also update the testing information without releasing a new version of the plugin. So the testing label and the last update date tell you different things. This is explained in the WordPress plugin warnings guidance.
If you pay for the plugin, make use of the developer’s support. Ask whether the specific plugin release supports your WordPress and PHP versions.
Check what the update needs to run
Before updating, check the plugin’s requirements.
These can include:
- A minimum WordPress version.
- A minimum PHP version.
- A particular version of another plugin it works with.
The minimum requirements and the Tested up to information are different details.
If an update requires a newer WordPress or PHP version than your website has, that needs attention first.
Do not make several unfamiliar changes at once just to get past a warning. Find out what your website needs and plan the work.
WordPress compatibility and PHP compatibility are separate checks
This is an easy one to get mixed up.
WordPress is the software you use to manage your website.
PHP is software running through your hosting that helps WordPress work.
A message about testing with your WordPress version does not confirm testing with every PHP version.
If your concern is a recent PHP change, check the developer’s PHP guidance as well. Do not rely on the WordPress testing label to answer a different compatibility question.
If you are unsure which versions you have, ask your host or someone you trust to help you check.
Read what the update is changing
The changelog is the list of changes included in a plugin release.
You do not need to understand every line, but look for mentions of:
- Security fixes.
- Compatibility changes.
- Known issues.
- Major feature changes.
- Extra steps needed after updating.
An update that adds a new design option needs a different decision from one that fixes a security problem affecting your installed version.
There is no set waiting period that makes every update safe.
Waiting a few days does not confirm that an update will work. Leaving a security fix unapplied while waiting for a label to change can create its own risk.
If a security issue affects your website and compatibility is unclear, seek help promptly so you can work out an appropriate next step.
Back up before you make changes
Before applying updates, make a fresh backup of your website files and database.
Check that it completed and that you know how you would restore it. WordPress recommends backing up before plugin updates in its website backup lesson.
Think about what has changed since your last backup, too.
If your website has received orders, bookings or enquiries, restoring an older copy could remove newer information.
For a busy website, your recovery plan needs to account for that.
Test important updates on a staging site
Where possible, use a staging site to test the update first.
This is a separate copy of your website where you can try changes before your customers are affected.
It is particularly useful for plugins that handle:
- Payments and checkout.
- Bookings.
- Membership access.
- Forms.
- Page layouts.
- Connections to other services.
The test copy should match your live setup as closely as practical.
Also, check that it cannot accidentally process real payments, email customers or trigger live automations.
After updating, test the feature itself. For a form plugin, that means sending a message and confirming delivery. For a membership plugin, it means checking that a test member can access the right content.
Simply seeing that the website loads is only the starting point.
What if you do not have a staging site?
Ask your hosting company whether your plan includes one.
If it does not, consider what the plugin does and how much disruption a problem could cause.
A small information website and a busy online shop have different needs.
If you decide to update the live website, have a fresh backup, allow time to check things afterwards and make sure help is available if needed. Updating plugins individually can make it easier to identify which change caused a problem.
If you would not know how to recover the website, arrange support before making a change you are worried about.
You do not need to turn an uncertain update into an emergency.
What if the plugin seems to have been abandoned?
An older plugin is not automatically broken or unsafe.
However, if you find several warning signs, such as no recent maintenance, unanswered support requests and unresolved compatibility problems, it is worth planning what comes next.
That may mean replacing it.
Before removing anything, check:
- What features depend on it.
- Whether it stores information you need.
- Whether your content uses its blocks or shortcodes.
- What needs to be transferred or rebuilt.
Do not delete an important plugin simply because another one looks similar. Replacing a plugin can involve more than installing its alternative.
So, should you update it?
My advice is to work through these questions:
- Is the developer still maintaining it?
- Does your website meet the update’s requirements?
- What does the update fix or change?
- Are there known problems affecting your setup?
- Can you test it and recover if something goes wrong?
The warning is one piece of information. Your decision also needs to consider how the plugin is used on your website.
You are not expected to know all of this just because you own a WordPress website.
For more on the everyday habits that help protect your site, read my guide to keeping your WordPress website safe.
If you are unsure, reach out to your hosting company, the plugin developer or an experienced WordPress expert you trust.
Want help working out your next step?
If you would like support while learning to manage your website, you can bring questions like this to the WordPress Learners Lounge.
We can look at what you are seeing and help you understand what to check next.
If you need someone to investigate or carry out the work for you, I also offer one-to-one help and done-for-you WordPress services.
Book a free 15-minute WordPress Clarity Call, and we can chat about what is happening with your website and the support you need.
