If a WordPress plugin update broke your website, avoid making several changes at once. First note what changed and what is affected. Then check whether you can still reach the dashboard, look for a recovery-mode email, and decide whether deactivating the plugin is safer than restoring a backup.
The goal is to get the site working without undoing more than necessary. If you are unsure how to handle files or a database, pause and ask your host or a WordPress professional for help.
Start with a quick, low-risk check
Before you troubleshoot, write down the plugin you updated, when the problem began, and what visitors see. Note whether the issue affects the whole site or only a page, form, or other feature. If you see an error message, save its wording or take a screenshot for support.
- Check the site in a private browser window or another browser to rule out a display issue on your device.
- Try the homepage and a few important pages, such as contact or booking pages.
- Check your email for a WordPress recovery-mode message. If WordPress detected a serious error, the message may include a special link to access the dashboard and troubleshoot the problem plugin.
- Avoid rerunning the update, deleting the plugin, or changing several settings before you know what is causing the problem.
If the site handles orders, appointments, or form submissions, consider whether visitors may be unable to complete those tasks. Keep a record of any new submissions or business activity while you work on recovery. That context matters if you later consider restoring a backup.
If you can still log in to WordPress
When the dashboard is available, start with the plugin you just updated. Deactivate it and check whether the affected pages work again. If they do, that is a useful sign that the plugin update is involved, though another plugin or theme may also be part of a conflict.
- Open the Plugins screen in the dashboard.
- Deactivate only the plugin linked to the change, rather than turning off every plugin at once.
- Check the public site and the dashboard again.
- If the site recovers, leave the plugin inactive while you confirm the cause and decide how to proceed.
Deactivating a plugin is different from deleting it. In general, deactivation stops the plugin from running; it does not automatically mean its settings or content are erased. Still, plugins vary in how they store information, so do not delete the plugin or remove its data unless you understand the effect.
If deactivating the plugin does not help, avoid guessing at fixes. A conflict with another plugin, the theme, or the site environment may be involved. A WordPress professional or your host can help inspect the error and narrow down the cause.
If you cannot access the dashboard
First check for a recovery-mode email and use its instructions if available. If you can get into the dashboard that way, deactivate the plugin causing the error and test the site.
If recovery mode is unavailable or the dashboard remains inaccessible, a plugin can sometimes be disabled through your hosting file manager or SFTP by changing its folder name. That approach involves editing site files, and a mistake can create more problems. If you are unfamiliar with those tools, contact your host or a WordPress professional before changing files.
When you ask for help, share the plugin name, the approximate time of the update, the error text, and whether the problem affects the whole site or specific pages. Avoid sending passwords in an ordinary email. Your support provider can tell you how to share access safely if it is needed.
Deactivate, roll back, or restore a backup?
These options do different things, so choose based on what you know about the problem.
- Deactivate the plugin: A good first test when the updated plugin is the likely cause. It stops the plugin from running while leaving the rest of the site in place.
- Roll back the plugin: Replaces the current plugin version with an earlier one. A rollback option may come from a tool or your host; do not assume WordPress has a general one-click rollback for every plugin. Confirm the method and have a backup before changing files or versions.
- Restore a backup: Replaces some or all of the site with an earlier copy. Depending on how the restore is done, it may affect files, the database, or both.
A full restore can undo newer site activity, including orders, form submissions, or other database changes made after the backup was created. Restoring files alone may not fix a problem if the database also needs attention. Ask what will be replaced and what recent data could be lost before approving a restore.
If the plugin update is the clear cause and deactivation brings the site back, a full backup restore may be more disruptive than necessary. If the damage goes beyond the plugin or you cannot safely isolate the cause, a restore may be appropriate, but get help assessing its scope first. For more on backup planning, see how long website backups should be kept.
Check the site after it comes back
A page loading again does not prove that every important part of the site is working. Once you have made a recovery change, check the site from a visitor’s perspective and in the dashboard.
- Open the homepage and the pages affected by the error.
- Test important forms and other key actions, including a test submission if that is appropriate for your site.
- Confirm you can still sign in and move around the WordPress dashboard.
- If a page still looks outdated, clear the relevant cache and check again.
- Record the plugin name, version if known, error, and recovery step so the next person helping you has a clear starting point.
After the immediate issue is resolved, avoid updating the same plugin again until you understand what failed and have a recovery plan. A staging environment for website changes can give you a place to check updates before they affect the live site.
When to contact your host or a developer
Ask for help if the dashboard is unavailable, the error continues after the plugin is deactivated, or you are not comfortable working with site files or database restores. Contact support promptly if important business functions are down or you are unsure whether a restore could remove newer data.
At Zevonix, we can roll back WordPress updates that break a site, and we can restore an individual file from a backup without undoing everything else. Zevonix hosts WordPress sites on isolated managed virtual servers, with checked nightly encrypted off-site backups, security monitoring, and malware scanning. If you want to understand the hosting setup, see managed hosting for WordPress.
Frequently asked questions
Can I roll back a WordPress plugin to its previous version?
Often, but the method depends on the plugin and the tools available through your host or site setup. Make a backup first, confirm the version you intend to use, and get help if you are unsure how to replace plugin files safely.
Will deactivating a plugin delete my website content or settings?
Deactivation generally stops a plugin from running; it is not the same as deleting it. Plugins handle settings and content differently, so avoid deleting the plugin or its data unless you know what that action will remove.
Should I restore a backup or just deactivate the plugin?
If the updated plugin is the likely cause and deactivation restores the site, start there. Consider a backup restore when the problem is broader or cannot be fixed safely another way, and first check whether newer site data could be affected.
How do I use WordPress recovery mode?
Look for a recovery-mode email from WordPress and follow the link and instructions it provides. If you do not receive one or cannot access the dashboard, contact your host or a WordPress professional rather than experimenting with site files.
How do I know whether the site is fixed?
Check the affected pages, key forms or actions, and the dashboard. If a specific feature still fails, or the error returns, treat the recovery as incomplete and ask for help.
Get the site stable before trying the update again
When a plugin update breaks a live site, start by identifying the change, checking recovery mode, and testing the updated plugin as the likely cause. Make one change at a time, protect newer site data, and ask for help before taking steps you are not comfortable with. If you need assistance recovering a WordPress site, contact Zevonix support.