To identify a plugin conflict, you can look for signs like unexpected behavior or errors on your website.
Detecting Conflicts
Here are some common symptoms and methods to detect a plugin conflict:
Resolving Conflicts
To resolve any plugin conflicts, creating a staging environment where you can safely disable and test plugins without affecting the live site is always best. We highly recommend WP Staging Pro; its free version can be found in your WordPress repository.
Let’s get started on how to eradicate plugin conflicts:
Begin by deactivating ALL plugins except the Kadence plugins. Then, flush your cache (we recommend Litespeed Caching or WP Rocket) to see if the issue is resolved. Re-enable each plugin one at a time, checking for the issue after activating each one. When the problem reappears, you’ve likely found the conflicting plugin.
Look for error logs in your application or website. In WordPress, for instance, you can enable debugging by adding define('WP_DEBUG', true);
to the wp-config.php
file. This will display or log errors that may point to the problematic plugin.
Open the browser console (usually by pressing F12
or right-clicking and selecting “Inspect”). Look for JavaScript errors or warnings that might indicate which plugin is causing an issue.
Check if all plugins are up-to-date and compatible with your website version. Some conflicts arise because a plugin is outdated.
Use the Health Check Plugin; it allows you to disable all plugins except specific ones, expediting the troubleshooting process. This plugin is best used in staging, and a free version can be found in your WordPress repository.
The Query Monitor Plugin is more technical and meant for expert-level troubleshooting, but it can give you insights into which plugins are adding files and filters. This plugin is best used in staging, and a free version can be found in your WordPress repository.
For issues relating to Kadence, please get in touch with them directly.