Plugin conflicts are common, but random deactivation on a live site is a poor diagnostic strategy. Use a controlled process that protects the site while narrowing the cause.
Start with the symptom
Write down exactly what fails, where it fails and what changed shortly before the issue appeared. A clear symptom is easier to reproduce and verify than a vague “the site is broken”.
Create a safe test path
Use a staging copy or maintenance window when possible. Confirm backups before changing plugins, themes, PHP versions or cache layers.
Isolate one layer at a time
Check WordPress core, theme, plugins, cache and server layers separately. Change one variable at a time so the result means something.
Verify the repair
A page loading once is not enough. Repeat the action that originally failed, test logged-in and logged-out states where relevant, and clear the caches involved.
Prevent the same failure
Record the conflicting versions, the permanent fix and the update path. If a workaround is temporary, make that explicit.
Tell us what you are trying to achieve. We’ll tell you what the WordPress work actually involves.
Start a project →