Black FridayCyber Monday 2026
14Days
15Hrs
22Mins
42Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

WordPress Plugin Conflict: Find the Plugin Breaking Your Website

A WordPress plugin conflict happens when two pieces of code interfere. Use staging, change one variable at a time, and record the exact conflict and the versions that work together.

wpallsolution 8 min read

WordPress plugin conflict is what you have when two pieces of code interfere with each other: two plugins, a plugin and the theme, or a plugin and a new WordPress or PHP version. The symptoms vary widely, from a broken layout to a fatal error. The reliable way to find the cause is a controlled test, and the important part is doing it safely and writing down the result. Our shorter guide How to find the plugin that broke your site gives the quick method; this guide adds the safety and documentation steps.

Quick answer

Write down exactly how to reproduce the problem. Make a backup and, if possible, a staging copy. On staging, switch to a default theme and deactivate all plugins; if the problem disappears, reactivate plugins in halves, then one by one, testing after each change. When the problem returns, you have found the pair or the single plugin. Record the plugin names and versions, WordPress and PHP versions, and what you saw. Then update, replace, or report the conflict to the plugin authors.

How this guide was prepared: the steps follow the WordPress and WooCommerce documentation listed under Sources, read on October 19, 2026. We did not reproduce your conflict, so the steps are research-based. Staging tools and plugin screens differ between hosts, and a conflict can involve your host’s own code too.

Before you change anything

  • Back up files and database. WordPress says to back up before changes and upgrades. See Is your WordPress backup really safe?
  • Prefer a staging copy. Deactivating plugins on a live store or membership site can interrupt orders and logins.
  • Do not troubleshoot during peak traffic if you must test on the live site, and tell your team.
  • Be careful with data. Some plugins store settings or data that you may lose if you delete them rather than deactivate.

WordPress plugin conflict: the decision tree

WordPress plugin conflict flowchart: five questions covering reproduction, staging, default theme, plugin bisect and version changes
Five questions, asked in order, isolate the conflict without breaking the live site.
  1. Can you reproduce the problem with exact steps? If not, write them first (Step 1).
  2. Do you have a staging copy and a backup? If not, create them first (Step 2).
  3. Does the problem disappear with a default theme? Then the theme is involved (Step 3).
  4. Does it disappear with all plugins off? Then bisect the plugins (Steps 4 and 5).
  5. Did it start after a version change? Record and report the versions (Steps 6 and 7).

Symptoms and likely causes

What you seeLikely causeStart with
Layout or buttons broken after an updateScript or style clashSteps 3 to 5
“Critical error” or a 500 errorFatal PHP errorSee WordPress critical error
Feature works alone but fails with another pluginTwo plugins hooking the same thingSteps 4 and 5
Editor or block editor fails to saveScript error or REST problemSee WordPress REST API error
Site slow after adding a pluginHeavy plugin, not a clashSee WordPress slow after installing a plugin
Started after a PHP or WordPress updatePlugin not compatible with that versionSteps 6 and 7

7 steps to find a WordPress plugin conflict

Step 1: Reproduce the problem and write down the steps

WooCommerce’s conflict-test guide says to recreate the same process each time for process-related problems. Write the exact steps, the page, the browser, whether you were logged in, and what you expect. Open the browser console and note any red errors, because the file name in an error often points at the plugin. A problem you cannot reproduce cannot be tested.

Step 2: Make a backup and a staging copy

WooCommerce recommends a backup and, ideally, a staging site: a clone of production where you can test without affecting visitors or revenue. Many hosts provide staging. Check that the staging copy shows the same problem before you start.

Step 3: Switch to a default theme

On staging, activate a default WordPress theme such as Twenty Twenty-Five (WooCommerce also suggests its Storefront theme for shops) and repeat the steps. If the problem disappears, the theme is part of the conflict, and you can continue with the theme and plugins together. If it stays, keep the default theme active for the next steps. Never use a design change on the live site as a test.

Step 4: Deactivate all plugins, then reactivate in halves

Deactivate all plugins on staging and test. If the problem is gone, reactivate half of them and test again. If the problem returns, the cause is in that half, otherwise it is in the other half. Repeat until you find one plugin, or a pair that causes it only together. This is a bisect, and it needs far fewer tests than activating one at a time on a site with many plugins. If you cannot log in, the WordPress FAQ shows how to deactivate plugins by renaming the plugins folder, and WP-CLI has wp plugin deactivate.

Step 5: Check must-use plugins and drop-ins

WooCommerce points out that some sites have a Must-Use or Drop-ins section in the plugins list. You cannot deactivate those from the list, but they can cause conflicts, and many hosts pre-install them, for example caching drop-ins. Some plugins also install helper plugins, so deactivating the parent deactivates them too. If the problem persists with everything off, ask your host about drop-ins.

Step 6: Check versions and requirements

WooCommerce recommends updating all plugins and themes first, since new releases include bug and security fixes and may already solve it. Then compare versions: which plugin, WordPress and PHP versions work and which break? Check each plugin’s page for the “tested up to” version and its changelog. Tools such as WP Rollback can restore previous plugin or theme versions, and Query Monitor can show PHP errors, database queries and HTTP API calls. Both are third-party plugins, so install them on staging, and judge their reliability yourself.

Step 7: Document the conflict and decide what to do

Write a short record: plugin A and B with versions, WordPress and PHP versions, the symptom, the exact steps, any error text, and what fixed it. Then choose: update or roll back one plugin, replace one with an alternative, adjust a setting that separates them, or report it to the plugin authors with your record (with secrets removed). Keep the record for the next update, and test again on staging whenever either plugin changes.

Version and hosting differences

  • A conflict can appear only on one PHP version, so note yours and your staging’s.
  • Page builders, caching and security plugins touch many parts of a site, so they are often involved.
  • Multisite, membership and shop sites need extra care: test logins and checkout, not only pages.
  • Staging environments differ from production in cache, CDN and email, so confirm the problem exists there first.

How to verify the fix

  • The original steps from Step 1 now give the expected result on staging, then on the live site.
  • You tested logged in and logged out, on mobile and desktop.
  • No new errors appear in the browser console or logs.
  • Your conflict record lists the working versions.

How to prevent it from happening again

Frequently asked questions

How do I know it is a conflict and not a bug?

If it disappears when another plugin or the theme is off, it is a conflict. If it persists with only one plugin and a default theme, it is a bug or setting in that plugin.

Can I test on the live site?

You can, but it is risky. Use staging, especially for shops and membership sites.

Is the newest plugin version always safer?

Often, but not always. Test it first and keep a way to roll back.

Who should I contact?

Contact the author of the plugin that breaks, and include your record. If two plugins are involved, contact both.

What to do next

Reproduce, isolate on staging, change one thing and write down the result. If the WordPress plugin conflict remains unexplained, bring your record to the plugin authors or your host. If you would like a person to look, wpallsolution offers independent plugin support and emergency WordPress fixes. We cannot promise a fix without seeing your setup.

Sources and official documentation

Last reviewed: October 19, 2026. WordPress is a trademark of the WordPress Foundation. wpallsolution is not affiliated with or endorsed by the WordPress Foundation or Automattic.

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us