Troubleshooting · Troubleshooting
How to Fix Plugin Conflicts in WordPress
Short answer
To fix a plugin conflict in WordPress, deactivate all plugins, then reactivate them one at a time until the problem returns. The last plugin you turned on is the likely cause. Then update it, replace it, or remove it, and check the page that broke.
Key takeaways
- A plugin conflict means two plugins, or a plugin and a theme, stop a feature or page from working as it should.
- Deactivate all plugins first, then reactivate them one at a time to find the one that brings the problem back.
- Troubleshooting Mode in Health Check tests plugins for your user session only, so visitors still see the live site.
- The debug log at wp-content/debug.log often names the plugin file behind a fatal error.
- Back up the site before you change plugins, and turn debug mode off when you finish.
- If the problem stays with all plugins off and a default theme on, the cause is likely the theme, core files, or the server.
What is a plugin conflict in WordPress?
A plugin conflict is a clash between two plugins, or between a plugin and a theme, that breaks a page or a feature.
Learn WordPress lists code incompatibility, JavaScript errors, and deprecated functions as common roots of plugin and theme conflicts, in its lesson on troubleshooting plugin and theme conflicts. A deprecated function is an old function that WordPress still runs but plans to remove.
A conflict is not the same as a broken plugin on its own. Two plugins can each work alone and still fail together when they load the same script, use the same function name, or change the same page in different ways.
What signs point to a plugin conflict?
A plugin conflict is likely when a problem starts right after you install, update, or activate a plugin.
Look for a blank white page, a critical error message, a form that will not submit, or an editor that will not load.
WordPress.org's common errors page lists plugin issues as a cause of both the white screen and a critical error.
| Sign | Likely cause | First test |
|---|---|---|
| Blank white page after an update | Fatal PHP error from a plugin | Turn on the debug log, then deactivate plugins |
| Critical error message | Plugin or theme fatal error | Open the Recovery Mode email, then check the log |
| Editor will not load | JavaScript clash between plugins | Open the browser console and note the file name |
| One form or page fails | Two plugins changing the same page | Deactivate the newest plugin first |
| Site fails only after activation | The new plugin clashes with an old one | Deactivate the new plugin and reload the page |
Timing is your best clue. Note the last change you made before the problem appeared, because that plugin is the first suspect.
What should you do before you change anything?
Make a full backup first, and note the exact symptom, page, and time it started.
Learn WordPress advises a full backup before making changes to a site, in its lesson on troubleshooting plugin and theme conflicts. A backup lets you restore the site if a fix makes things worse.
Write down the page that fails, the error message, and the last plugin or theme change. That record helps you test one change at a time instead of changing 3 things at once.
If your host offers a staging site, test there first. A staging site is a private copy of your live site where you test changes without affecting visitors.
How do you find the plugin that causes the problem?
Deactivate all plugins, check the site, then reactivate them one at a time until the problem returns.
This is the method WordPress.org's common errors page gives for a white screen: deactivate all plugins, then reactivate them one by one. The plugin that brings the error back is the suspect.
- Go to Plugins > Installed Plugins in the dashboard.
- Tick the checkbox next to Plugin to select all plugins.
- Choose Deactivate in Bulk Actions, then click Apply.
- Reload the broken page. If it works, a plugin caused the problem.
- Reactivate one plugin, reload the page, and repeat until the problem returns.
Change only one thing between each reload. If you reactivate 2 plugins at once, you will not know which one caused the failure.
If you have many plugins, test in small groups first, then test the plugins in the failing group one at a time. That narrows the list faster on a large site.
How do you use Troubleshooting Mode in Health Check?
Troubleshooting Mode gives you a clean session with all plugins off and a default theme on, while visitors still see the live site.
The Health Check & Troubleshooting plugin says Troubleshooting Mode gives a clean WordPress session where all plugins are disabled and a default theme is used, but only for your user until you disable it or log out. Its latest listed release, 1.7.1, was released on 25 July 2024, as of November 2026.
- Go to Plugins > Add New and search for “Health Check and Troubleshooting”.
- Install and activate the plugin.
- Go to Tools > Site Health, then open the Troubleshooting tab.
- Click Enable Troubleshooting Mode.
- Reactivate plugins one at a time from Plugins > Installed Plugins and reload the broken page after each one.
When you finish, turn Troubleshooting Mode off from the admin bar. If you get stuck in that mode, the plugin page says to clear your cookies, close all browser windows, or restart your computer to clear the cookie.
The plugin code is also kept in its official Health Check repository on GitHub, where its readme describes the same troubleshooting session.
What if you cannot open the WordPress dashboard?
Use Recovery Mode first, and if that fails, deactivate plugins by renaming their folders with FTP or File Manager.
Recovery Mode is a built-in WordPress feature introduced in version 5.2, according to the WordPress.org Recovery Mode page. WordPress sends an email to the site admin with a link to log in with Recovery Mode when a fatal PHP error occurs.
- Open the Recovery Mode email in the admin inbox and click its login link.
- Look for the notice that names the faulty plugin or theme.
- Go to Plugins and deactivate that plugin, then click Exit Recovery Mode.
If no email arrived, check spam, then use FTP. Open wp-content/plugins, right-click the suspect plugin folder, and add “-old” to its name, for example plugin-name-old. WordPress then deactivates that plugin.
To turn off every plugin at once, rename the whole plugins folder to plugins_old. WordPress.org's common errors page gives that exact folder name for this test. Rename it back to plugins before you reactivate plugins one at a time.
How do you read the debug log to name the plugin?
Turn on WP_DEBUG with logging, reload the broken page, then open wp-content/debug.log and look for a plugin folder name in the error.
WordPress.org's Debugging in WordPress page says WP_DEBUG is false by default, and WP_DEBUG_LOG needs WP_DEBUG set to true to do anything. Add these lines to wp-config.php, before the line that says “That's all, stop editing! Happy blogging.”:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Reload the broken page, then open wp-content/debug.log in File Manager or FTP. Look for the newest lines that name a file under wp-content/plugins/. That folder name is the plugin to test first.
The same debugging page warns that WP_DEBUG tools are meant for local testing and staging installs, not live sites. Keep WP_DEBUG_DISPLAY set to false on a live site so errors do not show to visitors, and set WP_DEBUG back to false when you finish.
How do you check JavaScript conflicts in the browser?
Open the browser console, reload the broken page, and note any red error that names a plugin script file.
MDN Web Docs says the JavaScript console reports errors encountered as the browser tries to run your code, in its guide to browser developer tools.
To open it, press Ctrl + Shift + I on Windows or Linux, or Cmd + Option + I on a Mac, then select the Console tab.
Chrome's Console overview says the Console has 2 main uses: viewing logged messages and running JavaScript. Reload the page with the console open and read the red messages first.
A console error that names a file under a plugin folder points to that plugin. A console error with no plugin name still helps: it tells you the clash is in JavaScript, not in PHP, so the debug log may stay empty.
How do you fix the conflict once you find the plugin?
Update the faulty plugin and the other plugin first, then replace or remove the faulty one if the problem stays.
Start with the least harmful fix. Update both plugins and WordPress core, clear the cache, and reload the page. An update can fix a clash caused by an old function or an old script.
If the problem stays, check the plugin page for its tested-up-to version and its last update date.
A plugin that has not been updated for a long time may not work with current WordPress. Read our guide on how to find abandoned WordPress plugins before you decide.
If you still need both plugins, contact the author of the faulty plugin with the error message, the plugin names and versions, and the steps to repeat the problem. Do not edit the plugin files yourself, because the next update will overwrite your change.
Two plugins can also clash because they both try to control the same feature, such as caching or forms. In that case, keep the plugin that runs the more important job and replace the other one.
How do you check that the fix worked?
Reload every page that failed, repeat the action that failed, and check the site in a private browser window.
A fix is not proven by one page loading once. Visit the home page, the page that failed, and the dashboard page where the error appeared. Submit the form, save a post, or run the checkout step that failed before.
Check the debug log again for new errors after your fix. If the log shows no new plugin error and the pages work, the fix holds. If you use a cache plugin, clear all caches first, or you may see an old cached page instead of the fixed one.
Keep a note of the plugin you removed or replaced and the date. That note saves time if the same clash returns after a later update.
When should you contact your host or the plugin author?
Contact the plugin author when one named plugin causes the clash, and contact your host when the problem stays with all plugins off.
WordPress.org's common errors page says a critical error can also come from an incompatible PHP version, a memory limit, or corrupted files. Those causes point to the server, not to a plugin.
Contact your host if the site still fails with all plugins off and a default theme on, or if the error log points to a server file.
Read our guide on how to update the PHP version in WordPress before you call, so you can name the exact version you need.
If the limit is memory, read our guide on fixing the allowed memory size exhausted error first.
Contact the plugin author if the debug log or console names one plugin, and include the error text, the WordPress version, the PHP version, and the other active plugins. A short, exact report gets a faster answer than a long description with no error text.
What mistakes should you avoid?
Do not change several plugins at once, do not leave debug mode on, and do not delete a plugin before you have a backup.
- Changing 2 plugins at once hides which change fixed the problem, so the clash can return later.
- Leaving WP_DEBUG on can show errors to visitors and fill the log file, so set it back to false when you finish.
- Deleting a plugin before a backup can lose its settings, so back up first.
- Updating every plugin at once after a clash can add a new clash, so update one at a time and reload the page.
- Ignoring the theme can waste time, because a theme can clash with a plugin in the same way. Switch to a default theme to test it: WordPress.org's common errors page names Twenty Twenty-One for WordPress 5.8 and below.
If you are unsure whether the problem is a plugin at all, read our guide on fixing the 500 internal server error to check the other common causes first.
Also read our guide on how many plugins is too many for WordPress to check whether plugin count is part of the problem.
Frequently asked questions
Can a plugin conflict break the whole site, or only one page?
It can do either. A fatal error in a plugin that loads on every page can break the whole site, while a clash on one form or editor screen may break only that page. Test the home page, the broken page, and the dashboard to see how wide the problem is.
Is it safe to deactivate all plugins at once?
Yes, if you have a backup first. Deactivating plugins does not delete their settings in most cases, and you can reactivate them one at a time. Do not delete plugins during the test, because deleting can remove settings and data that deactivating keeps.
How long does it take to find a plugin conflict?
It can take 10 to 30 minutes on a small site, and longer on a site with many plugins. The one-at-a-time test is slow but sure. Troubleshooting Mode and the debug log can shorten it by naming the suspect plugin before you start reactivating plugins.
What if the problem returns after I reactivate a plugin I need?
That plugin is the cause, so update it first and check its support page for a known clash. If no update fixes it, look for a different plugin that does the same job, or ask the author for a fix with the exact error message and the other plugin names.
Do I need to keep the Health Check plugin installed after the fix?
No. You can deactivate and delete it after you finish, since its Troubleshooting Mode is only needed while you test. Keep it only if you test plugin changes often and want the tool ready for the next clash.
Sources
- Troubleshooting your site: Plugin and theme conflicts Learn WordPress
- Common WordPress errors WordPress Developer Resources
- Debugging in WordPress WordPress Developer Resources
- Health Check & Troubleshooting WordPress.org
- Recovery Mode WordPress.org
- What are browser developer tools? MDN Web Docs
- Console overview Chrome for Developers
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.
