A plugin conflict happens when two or more plugins interfere with each other, or when a plugin is incompatible with your version of WordPress, your theme or the PHP version your server is running. The result is usually a broken feature, a white screen, a JavaScript error or something on the site simply stopping working for no obvious reason.
Why conflicts happen
WordPress is built to be extended by plugins. Most of the time this works fine. But plugins are built by different developers, often without detailed knowledge of what other plugins are running on the same site. When two plugins both try to do something similar (handle forms, load a particular library, modify checkout behaviour), they can get in each other’s way.
The most common triggers:
-
A plugin update changes how it works and breaks compatibility with something else
-
A new plugin is installed that conflicts with an existing one
-
A WordPress core update changes something that a plugin was relying on
-
A PHP version upgrade on the hosting server breaks a plugin that has not been maintained
How to identify a plugin conflict
The fastest way to confirm whether a plugin is the culprit is the deactivation test:
-
Make a backup of your site first
-
Deactivate all plugins at once (via FTP if the dashboard is inaccessible: rename the /wp-content/plugins/ folder to /wp-content/plugins-disabled/)
-
If the problem goes away, a plugin is causing it
-
Reactivate plugins one at a time, checking after each one, until the problem reappears
-
The last plugin you activated is the conflict source
If you cannot access the dashboard at all, you will need FTP or hosting file manager access to rename the plugins folder.
How to fix a plugin conflict
Once you have identified the conflicting plugin, you have a few options:
-
Check for an update: if the plugin has a recent update, install it. The conflict may already be patched
-
Check the plugin’s support forum: the WordPress.org plugin repository has a support tab for each plugin. Search for your specific conflict. Others may have reported it and a fix may exist
-
Contact the plugin developer: if it is a premium plugin, raise a support ticket with details of the conflict
-
Find an alternative: if the plugin is not actively maintained and the conflict cannot be resolved, replace it with a different plugin that does the same job
-
Remove one of the conflicting plugins: if you have two plugins doing similar things (two form plugins, two SEO plugins), you probably only need one
How to prevent plugin conflicts
-
Keep plugins updated, it reduces the chance of incompatibilities
-
Only install plugins from reputable sources with recent updates and active support
-
Do not install two plugins that do the same job
-
Test major updates on a staging site before applying them to the live site
-
Remove plugins you no longer use: even deactivated plugins can cause issues
-
Keep your WordPress core and PHP version current
A note on plugin quantity
There is no magic number for how many plugins is too many. Ten well-coded, well-maintained plugins will cause fewer problems than thirty poorly maintained ones. The question to ask of any plugin is: is this actively maintained, does it have a recent release, and does it have an active support forum? If the answer to any of those is no, think carefully before installing it.
Read next
If a plugin conflict has already broken your site, read WordPress site broken: what to do. For how regular maintenance prevents this kind of problem, see Do I need a WordPress maintenance plan.
For the bigger picture, our complete guide to WordPress for South African small businesses pulls all of this together.
Need a hand?
Plugin conflicts are one of the most common things we fix as part of our WordPress rescue service. If you are stuck, get in touch with a description of what is happening and we will sort it out.
Not sure which service fits? See everything we do with WordPress, from builds to rescues to ongoing care.
