Testing for Plugin Conflicts
If something isn’t working right, it’s always a good idea to test for a plugin conflict first.
What is a Plugin Conflict?
A plugin conflict is when code in one plugin causes functionality in another plugin to break. This could be due to a bug in one of the plugins or perhaps an oversight in how something was programmed that unexpectedly causes issues with another plugin.
How to Test for a Plugin Conflict
Follow these steps to test for a plugin conflict and identify the plugin that is causing the problem:
- Deactivate all plugins except for Wicked Block Builder
- Check to see if the issue you were having has gone away
- If it has, this means there is a conflict with another plugin. Re-activate the plugins one-by-one, re-check to see if the issue has reappeared and, if not, re-activate the next plugin in the list until the issue returns
- Once the issue reappears, tell us the name of the plugin that is causing the conflict and we’ll try to figure out why the conflict is occurring
- Occasionally a conflict can be caused by a theme. If the issue persists after deactivating all plugins, it’s always a good idea to temporarily switch the theme to a default WordPress theme such as TwentyTwentyOne to rule out the them as the culprit
Tip: if you have a lot of plugins, a shortcut is to reactivate the plugins in groups. For example, reactivate half of the plugins to start. If the issue returns, you know that it’s a plugin in that group. Now you can deactivate half of the plugins in that group to see if the issue goes away. Keep splitting the group in half until you identify which plugin is causing the conflict.
