WordPress plugin conflict: how to find it and fix it safely

A button stopped working, or the whole site went blank, right after you updated a plugin. That’s usually a WordPress plugin conflict: two plugins, or a plugin and your theme, trying to do the same thing in incompatible ways. The result ranges from a form that stops sending to a site that won’t load at all. Conflicts are one of the most common reasons a WordPress site breaks after an update, and the good news is you can find them methodically. Here’s how I track one down without making the site worse.

How do I know it’s a plugin conflict?

You’re probably looking at one if:

• Something broke right after you updated or installed a plugin
• A form, slider, menu or checkout works on some pages but not others
• The layout looks different when you’re logged in versus logged out
• An admin screen loads blank or spins forever
• You see a white screen or “There has been a critical error on this website”
• The browser console shows JavaScript errors naming plugin files

Why do plugins conflict?

Plugins are written by different people who can’t test against every other plugin. The usual causes:

1. Duplicate functions or classes. Two plugins bundle the same library in different versions, and PHP refuses to load both. This produces a fatal error.
2. JavaScript clashes. Two scripts load different versions of the same library, or one fails and stops the scripts after it from running. Forms and checkout are hit hardest.
3. Doing the same job twice. Two caching plugins, two SEO plugins, two security plugins. Each assumes it’s the only one.
4. Optimisation plugins rewriting code. Plugins that combine, minify or delay CSS and JavaScript can change the order other plugins depend on.
5. Outdated plugins. A plugin the developer stopped updating calls WordPress functions that have since changed.

Step 1: Back up and write down what changed

Before you touch anything, take a full backup of the files and database. Then note what changed recently: which plugins were updated, what was installed, whether the theme or WordPress itself updated, and whether the host changed the PHP version. Most conflicts follow a change within the last few days, so this list is often the shortcut to the answer.

Step 2: Read the errors

Turn on WordPress’s debug log (how to) and reproduce the problem. Fatal errors in wp-content/debug.log include the file path, which names the plugin. For front-end problems, open your browser’s developer tools on the broken page and check the Console tab. The error lines usually point to a specific plugin’s script.

If two different plugin names appear in the same error, you’ve probably found your pair.

Step 3: Test plugins one at a time, safely

The classic method is to deactivate all plugins, check the problem is gone, then reactivate them one by one, testing after each. On a live site that changes what every visitor sees, so use one of these instead:

• The Health Check & Troubleshooting plugin (WordPress.org) has a troubleshooting mode that disables plugins and switches to a default theme for your login only. Visitors see the normal site while you test.
• A staging copy. Many hosts create one in a click. Break it as much as you need.

When the problem returns after reactivating a plugin, that plugin is one half of the conflict. To find the other half, deactivate everything except that plugin and reactivate the others one at a time.

Step 4: Check the theme too

If the problem stays with every plugin off, switch to a default theme such as Twenty Twenty-Five, again in troubleshooting mode or on staging. Themes often bundle their own copies of libraries or override WooCommerce templates, so a theme can be the second party in a “plugin” conflict.

Step 5: Decide on the fix

Once you know the pair, you have a few options, in order of preference:

1. Update both if newer versions exist. The conflict may already be fixed.
2. Change a setting. If an optimisation plugin causes it, exclude the other plugin’s scripts from combining or delaying.
3. Replace one plugin with an alternative that does the same job, or remove it if a second plugin already covers that job.
4. Report it to both plugin developers with the error message. Good developers fix conflicts quickly.
5. Roll back the updated plugin to its previous version as a temporary fix, and plan a proper fix, because old versions stop receiving security updates.

What if the conflict only appeared after an update?

These are the most frustrating ones: they show up the morning after automatic updates ran overnight. Two habits prevent most of them. Test updates on a staging copy before they reach the live site, and update in small groups rather than “Update all”, so you know which update caused the problem. If your site did break after an update, my guide to what to do when a WordPress update broke your site walks through getting back online first.

How do I stop plugin conflicts happening again?

Most conflicts are preventable if you build a few habits:

• Keep the plugin list short. Every plugin is a possible conflict. Remove anything unused; deactivated plugins can still cause trouble through leftover files.
• One plugin per job. One cache, one SEO plugin, one security plugin, one form builder.
• Prefer well-maintained plugins. Check the last update date and support activity before installing.
• Avoid nulled premium plugins. Pirated copies are often modified and are a common source of both conflicts and malware.
• Watch optimisation plugins carefully. Many conflicts I see are caused by settings that combine or delay scripts. See why two cache plugins make a site slower.

Should I keep a note of what fixed it?

Yes. When you find a conflict, write down which plugins were involved, which versions, what the error was and what fixed it. Next time either plugin updates, check that note first. Conflicts that were fixed by a setting change can come back if a plugin update resets its options.

When should I get help?

Get help if the conflict is on a store’s checkout, if you can’t log in, or if the fix means choosing between two plugins your business relies on. Finding the cause is usually quick. Choosing the right replacement and testing it properly is where experience saves time. Plugin housekeeping and tested updates are part of every WordPress maintenance plan I run, and a one-off fix starts from $150.

Written by Sakib Islam, a WordPress developer who builds and looks after sites for businesses and agencies. About my work