Support

CoSchedule WordPress Plugin Conflicts

If you’re having trouble due to a plugin conflict that is not on the list below, please follow these steps.
  1. If CoSchedule is not behaving as expected, turn off all other plugins one at a time to identify which other plugin is causing the conflict.
  2. Take a screen recording of your entire browser window capturing the problem you’re running into and send it to us at support@coschedule.com. Include the name of the conflicting plugin.
Below are known WordPress plugin conflicts.

      • Bit.ly Official WordPress Plugin

        The Bit.ly Official WordPress Plugin will cause a conflict when using Google UTM tags. Since the link is already shortened when it enters the CoSchedule system, the UTM tags that are added will not do anything. Use CoSchedule's Bitly Integration instead.

        Disable XML-RPC Pingback

        The Disable XML-RPC Pingback plugin prevents CoSchedule from making requests to your blog. Disabling this plugin will allow CoSchedule to send and receive information from your WordPress blog.

        Easy PayPal Custom Fields

        The plugin Easy PayPal Custom Fields prevents us from saving posts to WordPress and blocks incoming requests. Currently, the only solution to this is to deactivate the Easy Paypal Custom Fields plugin.

        Easy WP SEO

        The Easy WP SEO plugin is not available in the WordPress plugin gallery but is a plugin that some users have downloaded and installed. This plugin is incompatible with CoSchedule. If you would like to use an SEO plugin with CoSchedule, several excellent options do not cause any conflict with CoSchedule, such as WordPress SEO by Yoast.

        Indeed Ultimate Affiliate Pro

        The Indeed Ultimate Affiliate Pro plugin prevents CoSchedule from making requests to your blog. Disabling this plugin will allow CoSchedule to send and receive information from your WordPress blog.

        iThemes Security

        iThemes currently disrupts connectivity to CoSchedule. However, it can be easily fixed with a change to the plugin's settings. For a fix, check out this page to learn how to fix the connection error.

        PilotPress

        The PilotPress plugin adjusts core WordPress user permissions to allow for customized user roles within a blog. This causes problems when CoSchedule attempts to sync post data to WordPress because PilotPress identifies CoSchedule as an unauthenticated user.

        Redirection

        The Redirection plugin can interfere with the ability of CoSchedule to connect with your WordPress site. Disabling this plugin will allow CoSchedule to connect.

        Role Scoper

        The WordPress plugin Role Scoper prevents CoSchedule from syncing authors and categories with WordPress. It is also no longer in active development (as of WP v3.7). The plugin page offers a few recommendations for alternative plugins.

        Root Relative URLs

        The plugin Root Relative URLs prevents CoSchedule from loading the JavaScript files it needs. Disabling the plugin is the solution to this problem.

        TinyPNG Image Compressor

        The TinyPNG WordPress plugin causes some Google Doc to WordPress conversions through CoSchedule to fail. Unfortunately, there is no workaround at the moment. If you're experiencing Google Docs converting failure, you'll need to uninstall TinyPNG plugin to resolve the issue.

        WishList Member

        The WishList Member WordPress plugin causes your WordPress categories to be inaccessible. You will not see your categories listed in WordPress with this plugin activated. This membership plugin is made to restrict access to categories to specific users of a WordPress blog, and in doing so, blocks CoSchedule from connecting.

        Wordfence

        Wordfence can prevent CoSchedule from connecting to your site. Disabling this plugin will allow CoSchedule to connect. Looking for a WordPress security that works with CoSchedule? We recommend Sucuri.

        WordPress Tweet Button

        The plugin WordPress Tweet Button has known conflicts that prevent CoSchedule from accessing an endpoint used to synchronize data. Without access to this endpoint, CoSchedule will display connection errors for the calendar.

        WP-SpamShield

        The plugin WP-SpamShield has known conflicts that prevent CoSchedule from accessing an endpoint used to synchronize data. Without access to this endpoint, CoSchedule will display connection errors for the calendar. Enabling our Static IP and whitelisting the IP through WP-SpamShield should resolve the issue.

        Yoast Duplicate Post

        The Yoast Duplicate Post plugin disrupts workflows within CoSchedule. The plugin will copy and paste your old WordPress info into a new post which will give CoSchedule a new ID. This will delete any work you have done within that project, including tasks, color label changes, and new social messages. We recommend using the duplicate feature built into CoSchedule.