Lorixen.
EN

Find a WordPress Plugin Conflict Without Taking Your Site Down

Short answer: Turn on troubleshooting mode from the Health Check plugin. Only your logged-in browser runs on the reduced set, so the public pages carry on exactly as before. Reproduce the broken feature, then switch plugins back on in halves until it breaks again, and narrow the last group down to a single suspect. Record every round. With 16 plugins, halving needs at most four rounds, which is why this method works on busy sites too.

Why a live site needs a different test

Deactivating every plugin on a live site means every visitor sees the change, including the contact form, the booking page or the checkout. Troubleshooting mode avoids that. Your session runs on a clean set of plugins while the public site keeps its normal set, so a customer can keep buying while you investigate.

Before you start

  1. Make a full backup of files and database, and confirm that the backup file opens.
  2. Write down the symptom exactly: the page address, the button or action, the error text if any, and the first date it went wrong.
  3. Check the plugin update history. A plugin or WordPress update that landed on that date is the first suspect.
  4. Switch on the debug log by placing these lines in wp-config.php, just before the section that marks the end of editable settings:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Entries land in wp-content/debug.log, and the third line stops error text from appearing on public pages.

Step 1: Turn on troubleshooting mode

Install and activate Health Check & Troubleshooting from the WordPress plugin directory. Open Site Health from the Tools menu and switch to the Troubleshooting tab. Enable troubleshooting mode, then load the broken page while logged in. The plugin is designed so that only your session uses the reduced plugin set.

If the feature works now, the cause is one of your normal plugins or your theme. If the fault persists, suspect the theme or a file you edited by hand. Test the theme separately, because the mode leaves your active theme running unless you choose otherwise.

Step 2: Split the plugin list in halves

Number your active plugins. Suppose you have 16 and label them 1 to 16. The method is simple:

Round Plugins enabled Result What it tells you
1 1 to 8 Breaks Culprit is in 1 to 8
2 1 to 4 Works Culprit is in 5 to 8
3 5 to 6 Breaks Culprit is in 5 or 6
4 5 Works Culprit is plugin 6
5 6 alone Breaks Confirmed

Each round, reload the same page in the same way and check the same thing. If the feature breaks only when two plugins run together, a single-plugin test will look clean. In that case, test the suspicious pair.

Step 3: Keep a log

A written log saves you from repeating a round. For each round, record the date, the plugins switched on, the page you tested, and the result. Note any message in debug.log that appears at that moment. Keep the log in a shared document so a developer or a colleague can read it later.

Step 4: Write the support ticket

Plugin developers respond faster to a precise report. Include:

  • WordPress version, PHP version and the active theme name with its version
  • The plugin name and version that caused the break
  • Numbered steps that reproduce the problem from a logged-out visitor's point of view
  • What you expected and what happened
  • The relevant lines from the debug log, with any customer data or keys removed
  • Which other plugins you tested, and whether the problem appeared with each of them

A ticket that says "the form stopped working after the update" gets questions. A ticket that says "step 3 fails with a 500 error when the form is submitted, and the log shows the same fatal error in line 214" gets a fix.

Step 5: Clean up

Once you know the culprit, do three things. Turn troubleshooting mode off so the public and private views match again. Decide whether to update the plugin, roll back to the previous version, or replace it. Finally, load the broken feature from a logged-out browser to confirm it works for visitors. Remove the debug lines from wp-config.php when you no longer need them, because a busy log file can slow down a site.

Rule out the false leads first

Some breakages look like plugin conflicts but come from somewhere else. Before you start halving, rule these out:

  • A cached copy. Your browser or caching layer may still hold the old script. Reload with the cache bypassed, or open the page in a private window.
  • A consent or cookie banner. A banner script that loads late can hide a button or block a form. Disable the banner plugin in your test round like any other plugin.
  • A hand-edited file. Code pasted into the theme's functions file or a custom snippet plugin is easy to forget. Check those first, because a snippet plugin is often missing from the plugin count you are halving.
  • A server limit. A form that fails only on large uploads may hit a PHP memory or upload limit, which shows in the host's error log rather than in the plugin list.

If the feature works in troubleshooting mode with every plugin off but fails with the full set, the method still applies. If it fails even with plugins off, the theme or the server is the next place to look.

FAQ

Will visitors notice the testing?

No. The reduced plugin set only applies to your logged-in browser session, so anonymous visitors keep the normal site for the whole test.

Does troubleshooting mode fix the conflict?

No. It only isolates the cause. You still need to update, change or replace the plugin, and then check that the feature works again.

What if I cannot log in to the admin area?

Open the file manager in your hosting panel and rename the suspect plugin folder, which deactivates it for everyone. Work from a backup if you can, and rename the folder back once you have tested. This is a last resort because every visitor is affected while the plugin is off.

Is a test copy of the site worth making first?

Yes, if a copy that mirrors the live site already exists. Otherwise, test on live only when customers are affected, since troubleshooting mode is safe there. A copy lets you try fixes without any risk to orders or bookings.

If the conflict keeps returning after you narrow it down, send us the symptom and your plugin list, and our studio will look at the code with you and recommend a fix, a replacement or a small custom feature.

Sources

WhatsAppBook a call