You updated a plugin (or installed a new one) and something broke. White screen of death, broken admin, failed checkout, missing functionality — these are all classic signs of a plugin conflict. Here's how to find and fix it systematically.
What Is a Plugin Conflict?
A plugin conflict occurs when two or more plugins try to use the same resources, register the same function names, or conflict on how they modify WordPress behavior. They're extremely common because WordPress plugins are built by thousands of independent developers with no central coordination.
Symptoms of a Plugin Conflict
- White screen of death (blank page with no error message)
- WordPress admin inaccessible
- Checkout or cart page broken
- Frontend layout broken (usually visual conflicts)
- Features that were working stopped after an update
- PHP errors appearing in the page source or error log
Step 1: Enable WordPress Debug Mode
Add these lines to your wp-config.php file before diagnosing:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
This writes errors to wp-content/debug.log without showing them to visitors. Check this log first — it often names the exact plugin and function causing the problem.
Step 2: The Deactivation Method
This is the definitive diagnosis technique:
- Deactivate ALL plugins except WooCommerce (if the issue is WooCommerce-related) or with no exceptions if the issue affects everything
- Test — does the problem persist?
- If the problem is gone, re-activate plugins one at a time
- Test after each re-activation
- The plugin that re-introduces the problem is your culprit
This takes 15–30 minutes but is definitive. Don't skip it.
Step 3: Use WordPress Safe Mode (WP 6.4+)
WordPress 6.4 introduced health check safe mode, which lets you test with plugins disabled without affecting your live visitors. Access it at yourdomain.com/wp-admin/?health-check-disable-plugins=1 (only works when logged in as admin).
If safe mode resolves your issue, you have a plugin conflict. Use the deactivation method to identify which plugin.
Step 4: Check for Theme Conflicts
If deactivating all plugins doesn't fix the issue, switch to a default WordPress theme (Twenty Twenty-Four) temporarily. If the problem resolves, your theme is the conflict source, not a plugin.
What to Do After You Find the Conflicting Plugin
Once you've identified the culprit, you have several options:
- Check for updates — if the conflict appeared after an update to the other plugin, the culprit may have a compatibility fix available
- Contact the plugin author — both plugin authors need to know about the conflict; they often have a fix
- Find an alternative plugin — if the conflict is between a specialty plugin and a core tool like WooCommerce, consider replacing the specialty plugin
- Use a code fix — in some cases, a developer can write a small compatibility patch
Preventing Plugin Conflicts
- Don't install more plugins than you need
- Test updates on a staging environment before applying to production
- Read plugin changelogs before updating — compatibility changes are usually documented
- Use a backup plugin that takes a backup before each update
Frequently Asked Questions
Two plugins conflict but I need both. What do I do?
First, report the conflict to both plugin authors — they may be able to fix it. If not, a developer can often write a small compatibility patch. Sometimes it's also possible to use hooks to modify how one plugin behaves to avoid the conflict.
I can't access wp-admin to deactivate plugins. Now what?
Use FTP or your host's file manager to rename the plugins folder from wp-content/plugins to wp-content/plugins_disabled. This deactivates all plugins. You can then access wp-admin and rename it back to re-activate one at a time.
Can a plugin conflict cause database corruption?
In rare cases, yes — particularly if a plugin has a bug in its database operations. Take a database backup before doing any major plugin updates.
How do I know if my site is running too many plugins?
Number isn't the issue — quality is. 20 well-coded plugins won't cause problems; 10 poorly written ones might. Check your site's query count and page generation time in Query Monitor (a plugin for developers). If a single plugin adds 50+ database queries, that's a red flag.