How to do a plugin/theme conflict test
Most the time when you find an issue on your site with SpotStack, it will be caused by a plugin or theme conflict. This can range from a simple CSS styling issue to a more complex issue where another plugin/theme is stopping SpotStack from functioning properly.
How to do a conflict test
- Deactivate all non SpotStack plugins and switch to a default WordPress theme (this will ensure site is as close to a clean install as possible).
- Check the site to see if the issue still exists. If the issue goes away after deactivating other plugins and switching theme then this means that either the theme or one of the plugins was conflicting with SpotStack. If the issue still exists then it is not a plugin or theme conflict.
- If it turns out to be a plugin/theme conflict, then you need to activate the plugins/theme one by one until you find the plugin/theme that causes the issue to come back.
- Once you have identified the conflict you can report the conflict to the developers of the plugin/theme and also to us.
NOTE: We suggest that you take a full backup of your site before deactivating plugins and themes as this will give you a restore point.
Doing a conflict test when your site is live to public
Because a conflict test involves deactivating plugins and switching themes, this will effect the look and functionality of your site (even if temporary). To not impact visitors to your site we strongly suggest creating a clone of your site and putting the clone onto a test domain to allow for proper testing to be done.