SEOSTUDIO™

How do I find which WordPress plugins are conflicting?

Reproduce the failure on a protected staging site. Start with an installed default theme and the minimum plugins needed for the workflow, then add other plugins one at a time. Retest the same action at every step. Confirm the suspected combination before changing production.

What does the problem look like?

A staff member can open a post but the block editor hangs when they add a custom block. Or a booking button responds on desktop but stops working on a smaller screen. Plugin interactions can cause those symptoms, as can the theme, cached assets, role-specific permissions, and differences between hosting environments.

Before you make changes

Confirm you have permission to change the staging copy and ask who can restore it. Back up both the database and the website files. Match production versions where practical and restrict access to the copy. Connect a payment sandbox or disable external callbacks and mail so tests cannot trigger customer-facing actions.

Step-by-step troubleshooting

  1. Write a repeatable test

    Record the page, user role, actions, expected outcome, and the first visible error. Save the versions shown under Tools → Site Health → Info. Remove domain details, customer records, or credentials before sharing any diagnostic information outside your team.

  2. Set up a minimal working baseline

    Confirm that the issue happens on staging with the full setup first. Switch to a default theme and temporarily deactivate optional plugins on staging. If the workflow depends on a particular plugin, keep that plugin and any declared dependencies available for the baseline.

  3. Test one thing at a time

    Re-enable a single plugin, repeat the exact workflow, and record pass or fail. Use the same URL, role, and cache procedure in each run. When a failure appears, rerun with that change removed to see whether the failure goes away.

  4. Confirm the smallest failing combination

    Keep the theme and environment fixed and test A alone, B alone, and A with B. Repeat with the site’s normal theme to see whether it changes the result. Capture the first relevant browser or host-log message tied to the test time.

  5. Verify one fix before deploying it

    Test a vendor-documented setting or supported fix against the failed workflow and a neighboring workflow. Deploy the narrow change during an agreed window, then repeat the smoke tests on the public site. Keep the previous settings so the change can be reversed quickly.

Worked example

A U.S. community theater adds a show announcement in the block editor. Saving an ordinary paragraph works, but the editor hangs when a staff member adds a custom event block. On staging, the block plugin works under a default theme. The issue returns only when a second plugin adds a custom editor toolbar. The team confirms the interaction under the staff role, tests a supported setting that excludes the event editor from the toolbar, and verifies both the ordinary post and event post before deploying that setting.

Common mistakes

  • Changing PHP, the theme, and several plugin versions in the same test.
  • Declaring the issue resolved after testing as an administrator when the report came from an editor.
  • Treating a working response in one warm browser tab as proof that public visitors see the same page.
  • Replacing the production database with staging and overwriting recent registrations or edits.

Verify the fix and plan a rollback

How to verify the fix

Verify the failure twice with the suspected setup, once with the isolated baseline or previous setting and again after the proposed fix. Test with the affected role and a second session. For a public interaction, check as a signed-out visitor and on the device class where the failure appeared.

If the change fails

On staging, restore the recorded plugin list and theme or use the staging snapshot. If you used Health Check’s compatible Troubleshooting Mode, exit it in the admin toolbar. If the verified change causes a new problem after deployment, revert that setting or the single scoped release, then recheck the critical workflow. Coordinate any production restore with the host so recent data can be preserved.

Practical follow-up questions

How can I tell whether one plugin or an interaction is responsible?

Hold the theme and role steady. Test the workflow without optional extensions, with A, with B, and with both. A failure in just the combined run supports an interaction. A failure with one extension by itself narrows the test to that extension and the baseline.

Is WordPress Site Health the same as Troubleshooting Mode?

The built-in Site Health screen shows status and configuration information. Troubleshooting Mode is a documented feature of the Health Check & Troubleshooting plugin. The official directory currently flags that plugin as untested with the last three major WordPress releases. Prefer staging if compatibility is uncertain.

Will using Troubleshooting Mode turn plugins off for everyone?

The mode presents a reduced configuration only in your logged-in session. Other users keep the site’s usual plugin and theme setup. Use a protected staging copy for changes that write data, charge payments, or send messages.

Why did a plugin look broken when I switched to a default theme?

Your workflow may depend on a template or code supplied by your normal theme. Choose a minimal baseline that still includes the feature. Once the plugin test is repeatable, run an explicit second test with the usual theme.

How should I test a problem that affects logged-out visitors only?

Run the workflow from a clean signed-out browser session on staging, at the same path and viewport size as the reported case. A session-specific troubleshooting mode cannot reproduce what a signed-out visitor sees.

Which information should I record before disabling a plugin?

Save the version and current settings, identify required dependencies, and note which workflows rely on it. Store screenshots or an available export with the staging notes. Have a named owner for re-enabling it and checking the result.

Why is a plugin still present after I disabled the optional plugins?

Your host may have installed a must-use plugin or a site may be managed through a network administrator. Check Site Health or the separate Must-Use screen, then ask the hosting or network owner before changing managed components.

Where do I look if a save breaks without a visible message?

On staging, record the timestamp and inspect the browser’s failed request. Ask the hosting team to match it to the application log. The WordPress debugging handbook documents private logging and turning error display off. Avoid leaving debugging enabled after the test.

Can I test a payment or membership plugin this way?

Use a protected copy with sandbox credentials and test accounts. Confirm the real service is disconnected before exercising renewal, checkout, or signup behavior. Check the applicable integration in its documented test mode.

What should a vendor be able to reproduce from my report?

The exact action, affected role, expected outcome, smallest failing plugin and theme combination, software versions, and a sanitized error snippet. Share a staging URL only through an authorized channel.

When is it worth replacing an extension instead of changing settings?

Consider replacement when a documented conflict remains unresolved and the existing workflow has a viable migration path. Test data export, required features, and a rollback on a copy before choosing a replacement.

Free tools and website checks

  • Website launch checklist (German)

    Use the browser checklist to track the main functional checks after your staging fix and export the list as text.

  • Free website checks (German)

    Choose a check based on what you need to verify. The redirect tool reports public HTTP status and destinations. It does not inspect WordPress plugin settings.

Frequently asked questions

Can I troubleshoot without uninstalling anything?

Yes. Staging activation and deactivation is enough to narrow the set of suspects. Leave removal, migration, and data cleanup for a separate verified change.

Does a green core Site Health status rule out a conflict?

No. Those checks cover selected configuration conditions. Reproduce the affected user workflow to test the behavior of a particular plugin combination.

How long do I leave a WordPress debug log enabled?

Enable it for the time needed to capture a reproducible staging test, then turn it off. Keep access restricted and share only the small relevant excerpt after removing sensitive values.

Official references and scope

This guide assumes self-hosted WordPress, a reproducible problem, and authorized access to staging or admin. A browser-local session cannot isolate the live database, host cache, scheduled jobs, or external services. If the admin area is unavailable, contact the host and use its documented recovery procedure.

Related guides