A plugin update that breaks something is usually fixed fastest by reverting to the version that worked, while the update’s own bug gets sorted out by its developer — WordPress doesn’t make this easy natively, since it only offers the current version for direct download, not a history of previous ones.
Before you buy, one quick look
Read-only. On the plugin’s page on WordPress.org, check the “Advanced View” or changelog for the version you just updated to, and look at its support forum for other people reporting the same problem.
A known, recently-reported regression in that specific version is common and confirms rollback is the right call rather than a coincidence specific to your site.
Premium plugins not hosted on WordPress.org won’t have this public view, but their own changelog or support channel usually serves the same purpose if you know where to look.
It’s worth noting the exact version number you’re currently on and the one you updated from, since “roll back” only means something specific once both numbers are known rather than a vague sense of “the version from last month.”
Plugin rollback to previous version
A plugin update broke something that worked before. We identify the last working version, roll back to it safely, and pause auto-updates until the new version's issue is fixed.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| A recent plugin update broke something that worked on the previous version | This fix covers it |
| You want to roll back but don’t know which earlier version last worked | This fix covers it, we identify it |
| The update failed to complete at all, rather than completing and breaking something | Plugin update failure resolution |
| A fatal error resulted from the update, not just broken functionality | Plugin fatal error isolation |
| You want to prevent future updates happening automatically | A separate settings change; ask if unsure how |
What you are seeing
- A feature that worked before a specific update stopped working immediately after
- Visual or functional changes you didn’t ask for appearing with the new version
- Other users reporting the same issue with the same version in the plugin’s support forum
- The previous version having worked reliably for a meaningful period before the update
- No fatal error, just broken or changed behaviour
Common causes
- A genuine bug introduced in the new version, not yet fixed by the developer
- A breaking change to the plugin’s settings format or database structure
- A dependency on a newer PHP or WordPress version than your site currently runs
- A feature intentionally removed or changed in the new version without adequate warning
- An update applied automatically with no chance to test it first
What we do
- Identify the last version that worked correctly, if you’re not certain
- Locate a safe, legitimate source for that previous version’s files
- Roll back the plugin to that version
- Disable automatic updates for this plugin until the newer version’s issue is resolved
- Confirm the previously broken feature works correctly again
- Note what to watch for before re-updating once a fix is available upstream
What is included
- The plugin rolled back to a confirmed working version
- Automatic updates disabled for this plugin to prevent it recurring unexpectedly
- Confirmation that the previously broken feature now works
- The pre-rollback backup, kept for 30 days
Not included
- Fixing the bug in the new version itself, which is the developer’s responsibility
- Permanently avoiding all future updates to this plugin, which carries its own risk
- Rolling back a database change the newer version already made, if one occurred
- Deciding when it’s safe to update again — that call is yours once the developer has actually fixed the bug
Questions about this fix
Is rolling back a plugin safe?
Generally yes for the plugin's own files, though if the new version changed how it stores data in your database, rolling back the files alone might not fully restore old behaviour — we check for that specifically before proceeding.
Will I miss security fixes by staying on an older version?
Potentially, which is why this is meant as a temporary measure while the newer version's problem gets resolved, not a permanent decision to freeze the plugin indefinitely.
How do you get an older version of a plugin?
WordPress.org keeps a version history for plugins hosted there, accessible through the plugin's advanced view; premium plugins usually require the previous download from the vendor directly, which we can request if needed.
Should I report the bug to the plugin developer myself?
It's worth doing, since developer awareness speeds up an official fix, and we can help identify exactly what to report if you'd like it framed technically.
What if the previous version has its own different bug?
We check the version history and any reports before rolling back, specifically to avoid trading one problem for another you'd then need fixing separately.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.