Plugin conflicts are one of the most common causes of broken WordPress sites. They occur when two plugins (or a plugin and the theme) try to do the same thing, load conflicting JavaScript, or override the same WordPress hooks. Here’s how to diagnose them quickly and cleanly.
Recognising a plugin conflict
Common symptoms:
- A layout broke immediately after installing or updating a plugin
- JavaScript errors appear in the browser console (F12 → Console)
- Certain pages show a white screen or PHP error
- A specific feature (menu, slider, form) stopped working
Step 1 — Use a staging site
Before touching production, duplicate the site to a staging environment. Most managed hosts (SiteGround, Cloudways, Kinsta) offer one-click staging. Diagnose on staging — never on a live site.
Step 2 — Deactivate all plugins at once
- Go to Plugins → Installed Plugins.
- Check the box at the top to select all plugins.
- From the Bulk Actions dropdown, choose Deactivate and click Apply.
- Reload the page that was broken.
If the issue is gone, a plugin was responsible. If the issue persists, it’s a theme-level problem.
Step 3 — Binary search to find the culprit
Instead of activating plugins one-by-one (slow), use a binary approach:
- Activate half your plugins. Does the issue appear?
- If yes: the conflict is in that half. Deactivate half of that set.
- If no: activate the other half.
- Repeat until you isolate the single plugin causing the issue.
This takes 5–6 steps regardless of how many plugins you have, versus dozens of steps with the one-by-one method.
Common conflicting plugins
- Multiple caching plugins — only ever use one caching plugin at a time
- Multiple SEO plugins (Yoast + Rank Math) — use only one
- jQuery version conflicts — old plugins that enqueue their own jQuery version will break other scripts
- Multiple form plugins loading conflicting CSS resets
- Security plugins blocking AJAX requests needed by the theme or WooCommerce
Step 4 — Check the browser console
Open F12 → Console and look for JavaScript errors. The error message usually includes the file name — if it’s from a plugin’s JS file, that’s your conflict source. Common JS errors:
$ is not defined— jQuery isn’t loading, or a script is loading before jQueryTypeError: X is not a function— two libraries defining the same global variableFailed to load resource 403— a security plugin is blocking a script
Reporting the conflict
When reporting a conflict to our support team, include:
- The exact plugin name and version
- A screenshot of the browser console errors
- Your WordPress version and PHP version
- A URL to the affected page (if accessible)