Fix Broken WordPress Functionality
How to Safely Test a WordPress Plugin Conflict and Find the Cause
Find the cause of a WordPress plugin conflict with safe isolation tests, a separate theme check, and a clear restoration checklist.

The safest way to test a WordPress plugin conflict is on a staging copy of your site, or in a troubleshooting mode that keeps changes within your administrator session. Make a full backup first, reproduce the broken behavior, and check that same behavior after every change. Then test the suspected plugin alone: a plugin that fails by itself is a different finding from two plugins that work separately but fail together.
Prepare a test you can repeat
A staging site is a separate copy used for testing rather than serving your normal visitors. WordPress’s troubleshooting lesson recommends a full backup before changes and describes staging as a controlled place to test without risking live-site functionality.
Before disabling anything, write down:
- The exact page or administration screen where the problem occurs.
- The action that triggers it.
- What should happen and what actually happens.
- Which plugins are active and which theme you use.
- The plugin most recently installed or updated.
For example, a hypothetical symptom might be: “On the booking page, selecting a date no longer opens the available times.” Keep checking that action—not merely whether the homepage loads.
Reproduce the symptom in your chosen testing environment before starting. If the booking problem does not occur there, a successful test cannot yet demonstrate that a plugin change fixed it.
If staging is unavailable, WordPress documents a troubleshooting mode in Health Check and Troubleshooting that lets you test without affecting what visitors see. Keep the following isolation steps within that troubleshooting mode rather than making ordinary site-wide changes on production.
For WordPress.com users, the supplied staging troubleshooting instructions apply to Business and Commerce plans. Do not assume that workflow is available on every WordPress.com plan.
Narrow the suspect, then rebuild the active set
If the problem began after a particular installation or update, start there. WordPress.com’s guide recommends deactivating the most recently installed or updated plugin first.
In your safe testing environment:
- Deactivate that plugin.
- Repeat the exact action that was broken.
- Record whether the symptom remains.
If the symptom disappears, you have found a plugin involved in the problem—not necessarily a plugin that is faulty on its own. It may be interacting with another plugin or the theme.
For a systematic test on staging, deactivate all plugins, check the symptom, and then reactivate plugins one at a time through Installed Plugins. Repeat your test after every activation. WordPress’s lesson explicitly recommends this sequence and making a note of the plugin enabled when the error returns.
Keep a small test log:
| Active plugins | Same symptom present? |
|---|---|
| None | Record the result |
| Booking plugin only | Record the result |
| Booking plugin plus the next plugin | Record the result |
These are example test states, not predicted results. Record the complete active set at each step. If the error returns after activating a plugin, the result implicates that plugin in the current combination; it does not prove that plugin fails alone.
If the symptom remains with every plugin deactivated, that test has not isolated an ordinary active plugin as the cause. Move to the separate theme check below rather than choosing a plugin to blame.
Distinguish a plugin failure from an interaction
Suppose the booking symptom returns when another plugin is activated. Now simplify the test again.
Test the suspect plugin alone. Deactivate the other plugins and activate only the suspect. WordPress.com recommends this check to determine whether it is the sole plugin cause.
- The same symptom occurs with the suspect alone: you have reproduced the problem without another active plugin. This is evidence against a plugin-to-plugin conflict, but it does not rule out the theme or another environmental cause.
- The suspect works alone: add the other plugins back in a controlled sequence, checking after each activation. The goal is to find the smallest combination you can reproduce consistently.
For a suspected pair, test each plugin separately, then both together. WordPress.com defines a plugin conflict as an error that appears only when two plugins are active together: each works by itself, and disabling either resolves the problem.
That distinction matters when reporting the issue. “Booking Plugin A fails alone” and “Plugin A and Plugin B work separately but fail together” give support teams different evidence. Include the failing action and the active combination, not just “there is a conflict.”
Test the theme separately
If plugin-only tests do not explain the symptom, isolate the theme:
- Leave all plugins deactivated.
- Test with your usual theme and record the result.
- Switch to a default WordPress theme, such as Twenty Twenty-Five.
- Repeat the same test with plugins still deactivated.
This is the sequence described in WordPress.com’s conflict guide. If the symptom occurs with your usual theme but not the default theme, the active theme may be involved. That is a useful comparison, not proof of the exact defective code.
If the broken feature requires a plugin to exist, record that it is unavailable with plugins disabled rather than calling it “fixed.” An absent booking form is not a working booking form.
If you cannot reach the dashboard
WordPress’s lesson describes using FTP or your hosting File Manager to rename the suspected plugin’s folder—for example, adding -old to its name. Renaming the folder deactivates that plugin automatically.
Use this as a targeted way to regain access or test a suspected plugin. Record the original folder name before changing it. When appropriate, restore that name and then check the plugin’s intended activation state in the dashboard; renaming is a diagnostic step, not your final site configuration.
What about a plugin conflict detector?
Directory-listed tools can help manage isolation, but their listings are feature claims, not independent proof of reliability:
- Conflict Finder advertises one-at-a-time activation and restoration of plugin, theme, and debugging states. Its listing also warns that disabled plugins, changed themes, and debug messages can be visible to logged-out visitors. Prefer staging; do not assume its tests are session-private.
- Conflict Guard says Safe Test Mode limits plugin changes to the administrator’s testing session. It also explicitly says its isolation system narrows possible causes rather than guaranteeing a single root cause.
- Plugin Detective describes disabling groups of plugins and using your “Fixed” or “Broken” responses to narrow the investigation. Its conclusions therefore depend on you checking the symptom consistently.
Whichever tool you use, confirm the suspected combination with the same repeatable test. A “conflict checker” label is not a diagnosis.
Restore and verify
Before finishing, return plugins, the theme, and any troubleshooting or debugging settings to their intended state. If restoring the original combination brings the problem back, do not describe the issue as resolved: you have identified a reproducible failing configuration.
Check the previously broken function again in the intended configuration. Exit session-limited troubleshooting, then check the site as a logged-out visitor to confirm visitors see the normal site—not your temporary test setup.
A useful outcome is specific: the original symptom is reproducible, a particular plugin or combination triggers it, and the site is no longer left in an accidental diagnostic state.

