All Collections
FAQ's and Troubleshooting
Third-Party Plugin Conflict Troubleshooting
Third-Party Plugin Conflict Troubleshooting

If your website issue gets fixed after deactivating all plugins, follow this guide to further troubleshoot.

Cristi avatar
Written by Cristi
Updated over a week ago

If you encounter any problems after installing or updating a 3rd party plugin, it's very likely that there's a conflict happening. Checking for plugin conflict is usually the first step of any WordPress issue troubleshooting, please follow the below steps in such cases:

1. It's recommended to take a full backup of the website before doing any changes to the website.

2. Please disable ALL the plugins at once. 

Do not deactivate important plugins which might take your whole site down, like any SSL plugin. If you are using any caching plugin, please make sure to clear the cache from the plugin settings before deactivating that plugin. 

If the issue is not fixed after deactivating ALL plugins, it is clearly not a plugin conflict and something else is causing the problem, feel free to let our Support Team know about it.

If the issue gets fixed after deactivating ALL plugins, proceed to the next steps:

2.1. Now, you need to enable the plugins one at a time. After activating each plugin,  refresh the site and see if the issue appears, so we can find the name of the plugin causing the problem(s).

2.2. Now, since you have the name of the plugin, you can activate it for further testing.

After activation, please switch to any of the default WordPress Themes, like Twenty Nineteen or any other theme which comes with the default WordPress installation, in Appearance > Themes.

If the issue occurs with the default WP theme as well, the problem is with the plugin itself and you need to contact the developer of that plugin about it. You can also find an alternative plugin here:

If the plugin is working fine with the default WordPress theme but not working fine with Divi only, in that case, you need to contact the plugin developer first and report the issue, as they know better their plugin's code.

They can quickly check where is the conflict and if it is something to be fixed at their end, they can fix it. If they suggest anything specific to be fixed at our end, please let us know with their findings and we can update our development team to fix those issues.

I hope this helps you to resolve any plugin conflict issues. 😃

Did this answer your question?