Site acts up after a plugin update and you don't know which plugin caused it.
Plugin conflicts are usually isolated within 20 minutes via a structured bisect on staging. Debugging live adds noise.
Try this first
- 1Reproduce precisely first: which page, which action, which browser, logged in or out. Without a repro, debugging is guessing.
- 2Switch to a stock theme (Twenty Twenty-Four) on staging. Still broken? It is a plugin, not the theme.
- 3Deactivate all plugins, confirm the issue is gone, then re-enable in blocks of five until it returns. Bisecting 40 plugins takes six clicks.
- 4Enable WP_DEBUG and WP_DEBUG_LOG in wp-config.php. The fatal trace in wp-content/debug.log usually points to the offending file directly.
- 5Update the culprit to its latest version or find an actively maintained alternative. Report the bug in the plugin support forum.
- 6Document the plugin stack and what each does, otherwise you'll hit the same wall in six months.
When to bring us in
If you can't reproduce or you find nothing after a full bisect, it likely sits in a hosting layer or mu-plugin. Ask your host or a WP engineer to look.
See also
- WordPress, plugins and theme have gone 6+ months without updatesOut-of-date WP is the number-one entry for malware. Don't just hit 'update all', back up first.
- Theme update broke the layout or threw a fatal errorThemes overwrite custom CSS on update unless you use a child theme.
- WordPress shows a blank screen after a plugin install or updateWSOD (white screen of death) is usually one crashing plugin. You isolate it.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.