Troubleshooting · Guide
How to Find Which Plugin Is Breaking Your Site
Short answer
Install the Health Check & Troubleshooting plugin, open Tools > Site Health > Troubleshooting, and enable Troubleshooting Mode. Turn plugins back on one at a time and repeat the failing action after each one. The plugin that makes the fault return is the cause.
Key takeaways
- Troubleshooting Mode turns off plugins and switches theme for your session only, while visitors see the normal site.
- Turn plugins back on one at a time and repeat the failing action after each one.
- If the fault stays with all plugins off, the theme, core, or server is more likely at fault.
- Confirm the cause by repeating the fault with the suspect on and off.
- WordPress 5.2 added Recovery Mode, which sends an email link after a fatal plugin error.
What does it mean when a plugin is causing a problem?
A plugin is causing a problem when one plugin, or two plugins working together, stops a page, feature, or action from working as it should.
The fault can be a white screen, a form that will not submit, a checkout that fails, or an editor that will not load. A plugin conflict is one common cause, but a single plugin can also fail on its own after an update or a PHP change.
Start by writing down what broke, when it broke, and what changed just before it broke. A recent plugin update, theme update, WordPress update, or PHP version change is often the first clue.
What do you need before you start?
You need a backup, a note of your active plugins, and a safe place to run the checks.
Back up files and the database before you change anything. The Learn WordPress troubleshooting lesson lists backups and error logs among the first steps for a fault like this.
Record which plugins are active now. Go to Plugins > Installed Plugins and take a screenshot or write the list down. That record lets you put the site back as it was if a check goes wrong.
Use a staging copy when you can. If you have no staging copy, use the Health Check plugin method below, which keeps visitors on the normal site while you check.
- A current backup of files and the database
- A list of active plugins and the active theme
- The exact page or action that fails, and how to repeat it
- 20 to 40 minutes, depending on how many plugins you have
How do you find the faulty plugin with Health Check?
Install Health Check & Troubleshooting, open Troubleshooting Mode, then turn plugins back on one at a time until the fault returns.
The Learn WordPress lesson describes this plugin as a tool made by the WordPress.org community to diagnose common issues, with a troubleshooting mode that lets you check your site without affecting what visitors see.
Follow these steps:
- Go to Plugins > Add New and search for “Health Check & Troubleshooting”.
- Click Install Now, then Activate.
- Go to Tools > Site Health and open the Troubleshooting tab.
- Click Enable Troubleshooting Mode.
- Repeat the action that failed. If it now works, a plugin or theme is at fault.
- Go to Plugins, click Enable while troubleshooting for one plugin, then repeat the action.
- Repeat step 6 for each plugin, one at a time, until the fault returns.
- When the fault returns, the last plugin you turned on is the suspect.
- Turn that plugin off again, then click Disable Troubleshooting Mode.
Troubleshooting Mode turns off all plugins and switches to a default theme for your session only. Visitors still see the normal site, as the Learn WordPress lesson states.
Do not save posts, submit orders, or change settings during this check unless you must. Troubleshooting Mode changes which code loads for you, but it does not create a separate database.
How do you find the faulty plugin by hand?
Turn off all plugins, check that the fault is gone, then turn them back on one at a time and check after each one.
This method is direct, but it changes the live site for every visitor while you work. Use it only on staging, or at a quiet time when you accept that some features will stop for a short while.
Follow these steps:
- Go to Plugins > Installed Plugins.
- Tick the checkbox at the top to select all plugins.
- Open Bulk actions, choose Deactivate, then click Apply.
- Load the page or repeat the action that failed.
- If the fault is gone, turn on one plugin.
- Repeat the failing action, then turn on the next plugin.
- Stop when the fault returns. The last plugin you turned on is the suspect.
The Learn WordPress lesson gives the same manual steps: select all, deactivate, then reactivate one at a time while you check the site after each activation.
If the fault stays after you turn off every plugin, the theme or WordPress core is more likely at fault. Switch to a default theme such as Twenty Twenty-Four and check again.
If the fault is still there with no plugins and a default theme, check the plugin conflict guide and your host error log next.
What if you cannot reach wp-admin at all?
Rename the plugins folder by FTP or file manager, which turns off every plugin at once without wp-admin.
This step helps when a plugin causes a white screen or a fatal error on every page, including the login page. You need file access through your host panel, SFTP, or SSH.
Follow these steps:
- Open your host file manager or SFTP client and go to
wp-content. - Rename the
pluginsfolder toplugins-off. - Load your site. WordPress will show no active plugins.
- If the site loads, rename the folder back to
plugins. - Go to Plugins > Installed Plugins and turn plugins back on one at a time.
WordPress 5.2 added Recovery Mode, which shows a message instead of a white screen when a plugin causes a fatal error. The wp-config page states that WordPress 5.2 introduced this mode, and that an email goes to the site admin address with a link to enter Recovery Mode.
Use that email link when you get it. Recovery Mode lets you log in and turn off the faulty plugin from inside wp-admin, without renaming folders by hand.
How do you tell a plugin fault from a theme fault?
Turn off the plugins first, then switch the theme, and see which change clears the fault.
Use this table to read the result of each check.
| Check | Result | What it points to |
|---|---|---|
| All plugins off | Fault gone | A plugin, or a pair of plugins |
| All plugins off | Fault stays | Theme, core, or server |
| Default theme on | Fault gone | Your theme or a theme plugin |
| Default theme on | Fault stays | A plugin or core |
| One plugin on | Fault returns | That plugin is the suspect |
| Two plugins on | Fault returns | A clash between those two |
The Learn WordPress lesson lists code conflicts, JavaScript errors, and calls to old functions as common causes of plugin and theme faults. A theme fault often shows in layout or in the editor, while a plugin fault often shows in one feature, such as checkout or a form.
If the fault only appears with two plugins on together, keep one off and look for a replacement for the other. Report the clash to both plugin authors, with the exact versions and the steps to repeat it.
How do you confirm you found the right plugin?
Repeat the fault with the suspect on, then confirm it clears with the suspect off, using the same steps both times.
A single failure can mislead you. Caching, a slow request, or a logged-in session can make a page fail once and then work. Repeat the action at least twice in each state before you decide.
Clear the cache between checks when a caching plugin is active. A cached page can hide a change, or show an old error after you fixed it. Open the page in a private browser window after you clear the cache.
Check the debug log as well. Turn on logging, repeat the fault, and look for the plugin folder name in the newest entries. The guide on finding slow plugins covers a related check when speed, not a hard error, is the symptom.
A slow plugin can also show as a timeout rather than a crash. The PHP manual gives the default execution limit as 30 seconds, so a script that runs past that limit stops with a fatal error instead of a page.
Write down the plugin name, version, WordPress version, and PHP version. You will need those four facts when you report the fault or look for a replacement.
What should you do after you find the faulty plugin?
Update it, roll it back, replace it, or report it, in that order, and keep it off until you have a fix.
First, check for an update. Go to Dashboard > Updates and see if a newer version of the plugin is listed. A fix for a known clash often ships within days of a WordPress release.
Second, check the plugin page on WordPress.org for its last update date and its tested-up-to version. A plugin with no update for over a year may not be kept up with current WordPress versions.
The Health Check plugin page is one example of a plugin page that lists its author, version, and update detail in the same place.
Third, look for a replacement that does the same job. Search the WordPress plugin directory for the same feature, check its last update date, and read recent reviews for reports of the same fault.
Fourth, report the fault to the plugin author. Give the plugin version, WordPress version, PHP version, theme name, and the exact steps to repeat the fault. A clear report is more likely to get a fix than a short message that says only that the site broke.
Keep the faulty plugin off while you wait. A broken checkout or form costs more than a missing feature, and a plugin that is off cannot break another page.
What mistakes should you avoid?
Do not turn on several plugins at once, do not skip the backup, and do not delete a plugin before you know what it held.
The most common mistake is turning on two or three plugins at a time to save time. That step hides which one caused the fault, and you must start the check again from the start.
A second mistake is running the manual method on a live shop at a busy time. Every plugin you turn off stops a feature for visitors. Use Troubleshooting Mode or staging for a live site, and keep the manual method for staging.
A third mistake is deleting the suspect plugin at once. Some plugins store settings, orders, or form entries in the database, and deleting the plugin can remove that data. Deactivate it first, export what you need, then decide whether to delete it.
Other mistakes to avoid:
- Changing the theme and the plugins at the same time, which hides the cause
- Forgetting to clear the cache between checks, which gives false results
- Ignoring the error log, which often names the exact file and line
- Updating every plugin at once after a fault, which adds new changes to the check
Check your PHP version after you finish. WordPress.org recommends PHP 8.3 or greater, with MySQL 8.4 or MariaDB 10.11 or greater, and notes that WordPress also runs on PHP 7.4 and MySQL 5.5.5 in legacy installs.
A plugin that needs a newer PHP version can fail on an old one, and the version check takes less than a minute in Tools > Site Health > Info.
Frequently asked questions
What is the difference between Troubleshooting Mode and turning plugins off by hand?
Troubleshooting Mode turns off all plugins and switches to a default theme for your session only. Visitors still see the normal site, so it is the safer choice for a live site. The manual method changes the site for everyone while you work.
How do I turn off all plugins if I cannot log in to wp-admin?
Rename the wp-content/plugins folder to plugins-off by FTP or file manager, load the site, then rename it back to plugins. WordPress will show no active plugins, and you can turn them back on one at a time from wp-admin.
How can I tell if the problem is a plugin or my theme?
A plugin fault often affects one feature, such as checkout or a form, while a theme fault often affects layout or the editor. Turn the plugins off first, then switch to a default theme, and see which change clears the fault.
What should I do with a plugin that breaks my site?
Check for an update first, then look for a replacement that does the same job. Report the fault to the plugin author with the plugin version, WordPress version, PHP version, theme name, and the steps to repeat it.
Is it safe to deactivate all plugins on a live site?
No, unless you use Troubleshooting Mode or a staging copy. Turning plugins off by hand changes the live site for every visitor, so some features stop working until you turn the plugins back on.
Sources
- Troubleshooting your site: Plugin and theme conflicts Learn WordPress
- Editing wp-config.php WordPress Developer Resources
- Health Check & Troubleshooting WordPress.org
- Requirements WordPress.org
- Debugging in WordPress WordPress Developer Resources
- Runtime Configuration PHP.net
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
