Can I just delete the broken plugin and reinstall an older version?

Sometimes, but only if you have a backup and you know the plugin did not change important database data during the update. If the plugin stores settings or content in the database, a file-only downgrade may not fully fix the problem.

Is it safer to roll back the plugin or the whole site?

If the update clearly caused the issue and you have a recent backup, restoring the whole site to the last good point is usually safest. If only one plugin or theme is responsible and the rest of the site is stable, a targeted rollback is better.

What if I cannot log into wp-admin after the update?

You can usually still recover through hosting file access, a file manager, SFTP, or your host’s backup restore tools. If you are not comfortable working at that level, get help rather than making blind changes.

How do I stop the problem from happening again?

Test updates on staging, keep backups before updates, and update one major component at a time when possible. For business-critical sites, a managed maintenance plan is usually the safest way to handle ongoing updates.

How to Roll Back a Bad WordPress Plugin or Theme Update

If a plugin or theme update broke your WordPress site, the safest fix is usually to restore the previous version from a backup or from the plugin/theme author’s release archive. Avoid guessing and avoid deleting files until you know exactly what changed, because the wrong rollback can make recovery harder.

The goal is not just to “go back one version.” You want to identify whether the update broke the front end, the admin area, or only a specific page or feature, then revert only the component that caused the problem. That approach reduces data loss and helps you avoid rolling back something that was actually working fine.

What a bad update usually looks like

A broken plugin or theme update does not always produce a dramatic crash. Sometimes the site still loads, but a key feature stops working, a layout shifts, a form no longer submits, or WordPress admin becomes unstable.

Common symptoms include:

A white screen, critical error, or 500 error right after updating
The homepage loads, but inner pages or the checkout break
Styling disappears because the theme’s CSS or template files changed
A plugin feature vanishes, such as sliders, forms, search, or blocks
wp-admin works partially, but settings pages or the editor fail
The site works for you but not for visitors, often because of caching

Sometimes the real issue is a compatibility mismatch: the new plugin version expects a newer WordPress core version, newer PHP version, or another plugin update that has not happened yet. In other cases, the update itself introduced a bug, a file conflict, or a bad settings migration.

Before you roll anything back

Back up first. Even when a rollback feels obvious, take a fresh backup of the database and files before changing versions. If the rollback goes wrong, the backup is your fastest escape route.

Also note what changed. Write down the plugin or theme name, the version number before and after the update if you know it, and what exactly broke. That record matters if you need to compare files, check changelogs, or ask the vendor for a fix.

If the site is still accessible, you may also want to pause other updates until you finish recovery. Updating more plugins during an incident can muddy the waters and create a second problem while you are trying to solve the first.

Safest rollback path: restore a backup

If you have a known-good backup from before the update, restoring just the files and database to that point is usually the cleanest option. Many hosts provide one-click restore tools, and some backup plugins can restore specific files or the full site.

Use this method when:

The update broke multiple parts of the site
You cannot easily tell whether the plugin, theme, or another change is responsible
The update changed database data as well as files
You need the fastest return to a working state

Be careful with partial restores. Restoring only files but not the database can leave you with mismatched plugin data, and restoring only the database can still leave the bad code in place. If you are unsure, read your host or backup plugin documentation carefully before restoring.

If you do not have a backup, roll back the exact version

If you need to downgrade a plugin or theme manually, the safest version is the one immediately before the update. Get it from the vendor’s release archive, official repository history, or your own staging copy if you have one.

For a plugin rollback

Confirm the plugin is the likely cause. If possible, compare the breakage with the update time.
Download the previous stable version from the plugin’s official source.
Deactivate the current version if WordPress still lets you.
Replace the plugin files with the older version.
Test the affected pages and admin screens immediately.

If you can still access wp-admin, some site owners use a rollback workflow that deactivates the plugin, uploads the previous ZIP, and then reactivates it. That can work, but it is only safe when you are certain the plugin did not store important data in a newer format during the update.

For a theme rollback

Check whether your site uses a child theme. If it does, do not overwrite the child theme unless you know it is safe.
Download the previous version of the parent theme from the author’s official source.
Replace the parent theme files carefully.
Reload the front end and admin customizer or site editor.

Theme rollbacks deserve extra caution because customizer settings, block theme templates, and site editor changes may depend on the updated theme structure. If you edit files directly, you can accidentally wipe out custom changes made since the last update.

How to tell whether the update really caused the problem

Not every “after update” problem is caused by the update itself. Sometimes the update simply exposed an old conflict that was already waiting to happen.

Check these basics before downgrading:

Clear any page cache, object cache, or CDN cache after the update
Try the site in a private browser window and from a second device
Disable other recently changed plugins if the site still loads
Check whether your PHP version changed recently on the host
Look for a support notice or known issue from the plugin or theme author

If the issue only appears in one browser, one page, or one role, you may be dealing with cached assets, JavaScript errors, or permission conflicts rather than a bad update. That is why a quick rollback can sometimes “work” while still leaving the underlying problem unresolved.

What not to do

When a site is down, it is tempting to try everything at once. That usually slows recovery.

Do not delete plugin or theme folders blindly unless you have a backup
Do not update more plugins while trying to fix one broken update
Do not reinstall WordPress core unless you have ruled out the plugin or theme
Do not assume the newest version is always the problem without checking symptoms
Do not keep the site in a half-rolled-back state for days

A half-finished rollback can be worse than the original bug because it creates version mismatch. The files say one thing, the database says another, and the cache may still serve the old version to visitors.

How to prevent the next bad update from becoming an outage

The best rollback is the one you never need in production. A simple update process can save you a lot of repair time later.

Test updates on staging first, especially for checkout, forms, and membership sites
Keep automatic backups running before updates are applied
Update one major plugin at a time when possible
Review changelogs for breaking changes and minimum version requirements
Keep a note of which plugins and themes are business-critical
Use a child theme for custom theme edits, not the parent theme

If your site depends on frequent updates but you do not have time to test them, a managed maintenance plan is often cheaper than one emergency repair. Mend’s Care Plan includes managed updates, backups, and monitoring, which helps catch problems before visitors do.

When a professional should handle the rollback

Call in a professional if the update affected a live store, membership area, booking flow, or other revenue-critical part of the site. The same is true if you do not know which component broke, if the rollback requires file-level access, or if the site has already had multiple failed recovery attempts.

This is also the right moment to get help if you need to preserve recent content changes while restoring only the broken plugin or theme version. That kind of targeted recovery is where careful engineering matters.

If you want a safe, backup-first fix without spending the afternoon on it, Mend can handle it for you. Start with a free Diagnosis, or go straight to Emergency Rescue if the site is down and you need fast help. Every paid fix comes with a plain-English report of what broke and what changed.

If you are troubleshooting right now

Use the simplest path that gets you back to a known-good state:

Take a fresh backup.
Identify the exact plugin or theme that changed.
Clear cache and confirm the issue is still real.
Restore the last good backup if you have it.
If needed, reinstall the previous stable version from the official source.
Test the affected pages immediately after rollback.

If that still does not restore the site, the issue may be a deeper compatibility problem, a database change, or a second conflict that the update exposed. In that case, it is faster to diagnose the root cause than to keep downgrading by trial and error.