Still need help? Submit a support ticket.

How do I check for conflicts?

Introduction

If you are having a problem with one of our plugins, then it could be either a conflict with another plugin (either another pootlepress plugin or any other plugin) or a conflict with some custom CSS you have in your theme.

This article will take you through how to test for a conflict.

Step 1 - testing for a plugin conflict

This is the most likely, so we will do this first. Ideally you should do this on a development or staging site (or at least at a time of low traffic on your live site)

1. Back up your site.

2. De-activate all other plugins (including other pootlepress plugins) taking care not to delete them. Leave the plugin you are having issues with activated.

3. Now test again to see if the issue you are having is gone. If it has gone, you have a plugin conflict. You should re-activate your plugins one at a time, testing the issue each time, to pin point which one is the ‘culprit’. Once you know which plugin is causing the conflict, you should submit a support ticket to us.

4. If the issue you have was still present then you do not have a plugin conflict and you should move onto step 2.

Step 2 - testing for a CSS conflict

Now you have tested for a plugin conflict the next step is to test to see if there is any custom CSS conflicting with our plugins. Again, ideally you should do this on a development or staging site (or at least at a time of low traffic on your live site)

1. Back up your site.

2. Remove any custom CSS from your site. If you keep your custom CSS in a child theme, the easiest thing to do is activate the original Canvas theme and then you will be able to test the issue without custom CSS. If you keep custom CSS in the original Canvas theme settings just copy and paste it out into a text editor (so you have it safe) and then remove it. 

3. Once you have made sure there is no custom CSS effecting your theme you can test the issue again. If your issue is gone, then you know it is a CSS conflict and you can work to remove the offending CSS.

4. If this does not fix the issue, you should submit a support ticket to us.