Skip to main content
All CollectionsTroubleshooting
Testing for WordPress conflicts
Testing for WordPress conflicts

How to determine if other plugins or themes on your WordPress site are conflicting with ConvertKit's WordPress plugins.

Updated over a week ago

Issues with ConvertKit's WordPress plugins may be caused by conflicts with other plugins or themes installed on the same site.

Use these steps to confirm if these conflicts are happening.

First things first, however:

Back up your site

The following steps should not cause damage to your site or its data as they are simply activating and deactivating plugins and themes.

Out of an abundance of caution, however, it's always wise to back up your site—and know how to restore it from the backup—before debugging it.

You can use a WordPress backup plugin like BackWPup or UpdraftPlus to back up your site.

Your hosting provider may also help back up your site regularly. If so, check if its latest backup is recent enough to rely on.

We do not recommend proceeding with the rest of the steps unless you have a site backup.

You've backed up your site?

Then, let's get troubleshooting.

Test your plugins

WordPress issues are often due to plugin conflicts—in other words, the ConvertKit plugin isn't fully compatible with another plugin you've installed on your site. Let's check if this is the case.

Go to Plugins in your WordPress sidebar > Add New Plugin. Install and activate the Health Check & Troubleshooting plugin.

Then, go to the Plugins page and click the Troubleshoot option under the Health Check & Troubleshooting plugin's name.

Your site will enter troubleshooting mode, where all your plugins (except for Health Check & Troubleshooting) will be disabled.

If you visit your site, it'll look as if it doesn't have any plugins enabled. But your site visitors' experience is unaffected—they'll continue to be able to use your site as if your plugins haven't been disabled.

Next, scroll down the plugins list and click the Enable while troubleshooting option for the ConvertKit plugin you're troubleshooting. For example, this could be the main ConvertKit plugin or the ConvertKit for WooCommerce plugin.

You'll also need to enable any other plugins that are needed for the ConvertKit plugin to work. This would be the WooCommerce plugin if you're troubleshooting the ConvertKit for WooCommerce plugin, for instance.

Next, go to Settings > Permalinks in your WordPress sidebar, and then click the Save Changes button at the bottom of the Permalinks screen without actually changing anything.

Doing this sounds funny, but it refreshes your site's permalinks, which is important for debugging.

Finally, try to recreate the issue that caused site errors earlier—such as trying to navigate to a certain setting or click a certain option.

If you encounter the issue again with all other plugins still disabled, please contact our support team for further assistance, sharing details on the issue and how you've tried to troubleshoot it using the Health Check & Troubleshooting plugin.

If you don't encounter the issue, enable another of your plugins and check if the issue still crops up. Repeat this process for all of your plugins, enabling them one at a time, until you encounter the issue again.

The last plugin you activated just before the issue occurred again is likely to be the cause of the errors. Contact its support team for further assistance.

If you don't encounter the issue even after re-enabling all your plugins one by one, then it probably isn't due to a plugin conflict. In this case, move on to step two.

Regardless of the outcome of this current step, click the Disable Troubleshooting Mode button at the top of your Plugins list to disable the Health Check & Troubleshooting plugin's troubleshooting mode when you've finished troubleshooting your plugins.

Activate a default theme

Now, you'll check for compatibility issues between the ConvertKit plugin and your WordPress theme.

Do this by going to Appearance > Themes in the WordPress sidebar and activating a default WordPress theme for your site. These are the free themes included by default with most WordPress installations, with names like Twenty Twenty-Four, Twenty Twenty-Three, and Twenty Twenty-Two.

If you don't have at least one default theme installed on your site, download them for free on WordPress.org and install them manually.

After activating a default theme, refresh your permalinks just like before. Then, do the same steps that had caused site errors earlier.

Does the issue persist when the default theme is active?

If it does not persist, then the theme you had active before switching to the default theme is likely the cause of the issue! Contact that theme's support team for further assistance.

If it continues to persist, then try testing your plugins individually again using step one above, with the Health Check & Troubleshooting plugin activated, to discover which one may be giving issues. Contact the relevant plugin's support team for further assistance after that.

If you're using WordPress caching, it may affect how changes are applied or how things work. To avoid issues, please whitelist us or disable any unnecessary caching plugins.

Did this answer your question?