2. Download name mismatch and no item_id specified

In order for the license updater to receive updates from the correct download on your site, the item_name and item_id keys are included in the array demonstrated above. It is not necessary to include both. If both are present, the item_id value will be used and item_name will be disregarded.

If only item_name is used, it is critical that the value matches exactly the download's actual title. If the title is not an exact match, update notifications will not be shown. For this reason, we recommend using item_id instead.

3. Using a security plugin or htaccess rules that blocks the ?edd_action=get_version/activate_license requests

Some plugins and htaccess rules block get variables like the one above because they're commonly used by attackers. Look for these settings and make sure they're off.

4. Why isn't it working on my multisite setup?

The custom updater only works when the plugin is active.

If you have activated a plugin on a single sub site, only that site can check for updates, the network admin cannot.

That means in order to get updates to show up, you must:

Activate plugin on sub site

Activate license key on sub site

Visit Plugins page on sub site (or just trigger the update check somehow)

This caches the available plugin updates in a network-wide transient

Now you can visit Network → Plugins and see the update

5. Why does my plugin always show there's an update?

The updater class in your plugin had a bug before version 1.6. Update to 1.6 or higher and this issue will be resolved.

6. Incorrect __FILE__ parameter provided to updater class

If you are extending the updater class from a file other than the main plugin file, add a define('YOUR_PREFIX_PLUGIN_FILE', __FILE__ ); to the main plugin file, and then instead of calling __FILE__ as the second parameter of the new EDD_SL_Plugin_Updater class, call YOUR_PREFIX_PLUGIN_FILE there.