A conflict is a repeatable failure involving a plugin, another plugin or the theme. Find a reproducible case before changing the site's whole setup.
Record the symptom and protect the site
Write down the affected URL, exact action, visible error and time the problem began. Note recent updates or settings changes. Check whether the problem happens while logged out and in a private browser window. A cached page or browser extension can confuse the diagnosis.
Take a complete backup and confirm hosting access. Prefer a staging copy, particularly for stores, memberships and forms. Disabling plugins on production can remove critical functions for every visitor.
Use staging or a scoped session
On staging, reproduce the issue with the current setup before disabling anything. If it cannot be reproduced, compare the environments: versions, settings, data and caching.
Health Check & Troubleshooting documents a troubleshooting mode that disables plugins and uses a default theme for the current user's session. It is designed to leave other visitors unaffected. Back up first and retain a recovery route; this session is not a complete substitute for staging, especially for payment, background or visitor-only behavior.
At the October 7, 2026 check, its directory metadata declares testing through WordPress 6.6.10, with the last update in July 2024. Compatibility with WordPress 7.1 is not established by that listing. Prefer staging on a current site, and verify the tool on an isolated copy before relying on it.
Use the plugin's documented troubleshooting controls. Avoid confusing session-specific controls with the normal Installed Plugins screen, which changes the actual site's active plugins.
Isolate the cause
- Confirm the error with the original configuration.
- Establish a baseline with plugins disabled in the test environment. Use a suitable default theme when testing theme involvement.
- Re-enable the suspected plugin and reproduce the same action.
- Add other relevant plugins one at a time, repeating the action after each.
- When the error returns, verify the suspected pair in both enabled and disabled states.
- Restore the original test configuration and confirm the result is repeatable.
A failure with one plugin alone may be that plugin's own error rather than a conflict. A feature also cannot be tested meaningfully if you disabled the plugin that supplies it. Keep the baseline appropriate to the task.
Resolve and report
Check official changelogs and support documentation for the identified components. Update supported versions on staging or test the documented workaround. Avoid keeping an outdated vulnerable version indefinitely just because it removes the symptom.
Send the responsible developer a short reproduction: versions, active theme, plugin pair, steps and expected versus actual behavior. Remove credentials and personal data from logs.
After the fix, exit troubleshooting mode or restore the staged configuration. Check the public site, forms and any checkout flow. Record the final change so the next update can be tested against the same case.
If admin is inaccessible, follow the white-screen recovery guide and involve the host. Do not delete plugin files at random.
Sources & verification
Sources checked October 5, 2026. Documented behavior is distinct from hands-on testing.