Automatic Updates For Private And Commercial Plugins

Last updated on December 17, 2014.

Since time immemorial, only plugins hosted in the official plugin directory have supported automatic updates. Now, I’ve written a PHP library that you can use to add automatic update capabilities to any plugin. Public, private and commercial plugins alike – all can now enjoy the benefits of automatic update notifications and one-click upgrades.

The custom update checker integrates closely with the upgrade system already built into WordPress, producing a seamless user experience. Observe :

An upgrade notice for a privately hosted plugin.

An upgrade notice for a privately hosted plugin.

The version information window with placeholder data

The version information window with placeholder data



This library is released under the MIT License and is distributed free of charge. If you find it useful, consider making a donation.

Quick-start Guide

This section describes the quickest way to get automatic updates working for your plugin. Here’s what you’ll need to do: create a metadata file for your plugin, host it somewhere publicly accessible, and tell the update checker where to find it.

Lets start with the metadata. Copy the JSON code below into a new file and replace the placeholder values with your plugin’s info.

    "name" : "My Cool Plugin",
    "slug" : "my-cool-plugin",
    "download_url" : "",
    "version" : "2.0",
    "author" : "John Smith",
    "sections" : {
        "description" : "Plugin description here. Basic HTML allowed."

(This is the minimal amount data required to make automatic updates work. In most cases, you will probably want to add a couple more fields. See the metadata docs below for details.)

Most of the fields should be pretty self-explanatory, with one possible exception – the “slug”. WordPress expects all plugins that support automatic updates to have a unique textual identifier called the “slug”. Normally, slugs are assigned by the official plugin directory. For a private/commercial plugin that’s hosted elsewhere you’ll have to make something up. If unsure, just use the plugin’s file name without the “.php” extension (my-cool-plugin/my-cool-plugin.php becomes my-cool-plugin).

Upload the metadata file you just created to your web server. It doesn’t matter where exactly you put the file or how you name it. The important thing is for its URL to be accessible from wherever someone might install your plugin.

Next, copy the “update-checker” directory from the client library archive to your plugin’s directory. Then fire up your favourite code editor and add the following lines to the top of your plugin file:

require 'plugin-updates/plugin-update-checker.php';
$MyUpdateChecker = PucFactory::buildUpdateChecker(

If you followed my advice and used the plugin’s file name as the slug, you can omit the third parameter of the PucFactory::buildUpdateChecker() call.

Tip: Sometimes you’ll run into a situation where another active plugin is also using this update checker. As a result, there could be several different versions of the library loaded at the same time. The above code snippet will always give you the latest available version. This can be a problem if your plugin expects an older version and is not API-compatible with the latest version.

To use a specific version of the update checker (e.g. the one included with your plugin), instantiate the PluginUpdateChecker_x_y class directly. Replace x and y with the major and minor version numbers:

//Use version 1.6 of the update checker.
require 'plugin-updates/plugin-update-checker.php';
$MyUpdateChecker = new PluginUpdateChecker_1_6 (

And that, believe it or not, is it.

The PluginUpdateChecker class will handle the rest. It’ll check the metadata file every 12 hours and, if it discovers that a new version has been released, twiddle the right bits in the undocumented WP API to make it show up as a standard upgrade notification in the “Plugins” tab. Assuming you’ve provided a valid download_url, users will be able to install the update with a single click.

Tip: When creating the ZIP file for an update, put all plugin files inside a directory. The directory name should match the plugin slug. Do not put the files at the root of the ZIP archive – it can cause subtle bugs and errors when someone ties to install the update.

The rest of this post will be devoted to a more in-depth discussion of the update checker class and the metadata format.

The PluginUpdateChecker class

This class is the core of the update checker. It’s also the only part of the updater that you should need to deal with unless you decide to  extend the library yourself.

Class constructor

All configuration settings should be specified by passing them to the PucFactory::buildUpdateChecker() factory method, or directly to the PluginUpdateChecker constructor. Both takes the following parameters:

  • $metadataUrl – The full URL of the plugin’s metadata file.
  • $pluginFile – The path to the plugin’s file. In most cases you can simply use the __FILE__ constant here.
  • $slug – The plugin’s ‘slug’. If not specified, the filename part of $pluginFile (sans “.php”) will be used as the slug.
  • $checkPeriod – How often to check for updates (in hours). Defaults to checking every 12 hours. Set to zero to disable automatic update checks.
  • $optionName – Where to store book-keeping info about updates. Defaults to “external_updates-$slug”.


Manually trigger an update check. This is especially useful when you’ve disabled automatic checks by setting $checkPeriod (above) to zero. This method takes no parameters and returns nothing.


Register a callback for filtering query arguments. Whenever the update checker needs to retrieve the metadata file, it will first run each filter callback and attach the query arguments that they return to the metadata URL. This lets you pass arbitrary data to the server hosting the metadata. For example, commercial plugins could use it to implement some kind of authorization scheme where only users that have the right “key” get automatic updates.

The callback function will be passed an associative array of query arguments and should return a modified array. By default, the update checker will add these arguments to the metadata URL:

  • installed_version – set to the currently installed version of the plugin.
  • checking_for_updates – set to 1 if checking for updates, absent otherwise (i.e. when loading data for the “Plugin Information” box).

This method takes one parameter – the callback function.


Register a callback for filtering the various options passed to the built-in helper function wp_remote_get that the update checker uses to periodically download plugin metadata. The callback function should take one argument – an associative array of arguments – and return a modified array or arguments. See the WP documentation on wp_remote_get for details about what arguments are available and how they work.

This method takes one parameter – the callback function.


Register a callback for filtering plugin info retrieved from the metadata URL.

The callback function should take two arguments. If the metadata was retrieved successfully, the first argument passed will be an instance of PluginInfo (see the source for a description of this class). Otherwise, it will be NULL. The second argument will be the corresponding return value of wp_remote_get (see WP docs for details). The callback function should return a new or modified instance of PluginInfo or NULL.

This method takes one parameter – the callback function.

Metadata format

The automatic update system uses a JSON-based file format to describe plugins.  Essentially, the entire file is one big JSON-encoded object (AKA hash-table or associative array). Each field – or array key – represents a piece of information about the latest version of the plugin. The full description of all available fields is here.

For the sake of simplicity, both general metadata and update-related information are stored in the same file. If this is undesirable, you can replace the plain JSON file with a script that checks for the presence of the the “checking_for_updates” query parameter and emits just the update-related fields if its set to “1”.


Your plugin must be active for updates to work. The update checker is just another piece of PHP code loaded and run by your plugin, and it won’t be run if the plugin is inactive.

One consequence of this that may not be immediately obvious is that on a multisite installation updates will only show up if the plugin is active on the main site. This is because update notifications usually appear in the network admin, and only plugins active on the main site are loaded in that case. The main site of a WordPress network is the one that was created first and has the path “/” in the Sites -> All Sites list.

Related posts :

297 Responses to “Automatic Updates For Private And Commercial Plugins”

  1. Jānis Elsts says:

    Check the directory structure of your ZIP file. All plugin files should be inside a “my-plugin-pro” directory. If the files are at the root of the archive instead, that can cause all kinds of problems with update installation.

  2. thaikolj says:

    Thanks a lot for this great function!

  3. John says:

    That was totally it! Thanks a TON this is a great plugin.

  4. Dillon says:

    I apologize if this is a vague question, but do you know of any reason why this library would not work with my host, WPEngine?

  5. Jānis Elsts says:

    No, I have no idea why it wouldn’t work with WPEngine. Can you provide any more details? What exactly seems to be wrong?

  6. Dillon says:

    When I attempt to update the plugin, WordPress says it “Could not remove the old plugin”. Nothing seems to show with debug turned on either.
    I had the library working on a local server, so I figured it could have to do with something that my host is preventing as a security measure. Thought I should check to see if you’ve had other people experience anything similar with WPEngine.

  7. Jānis Elsts says:

    The actual update is handled by WordPress itself and not this library. Here are a few ideas anyway:

    – File permissions: Does WordPress/PHP have write access to the plugin directory?

    – ZIP file structure: Are plugin files in a subdirectory that matches the plugin slug, or are they at the root of the archive? They should be in a directory. Placing them at the root can cause all kinds of seemingly unrelated errors during update installation.

    – Locked files: Could there be anything that’s keeping one of the plugin files open while you’re trying to install an update? I don’t think that would cause problems on WPEngine specifically since they presumably use *nix and not Windows, but it’s a possibility.

  8. Dillon says:

    Okay great, I will look into these and see if I get anywhere. I appreciate you taking the time to assist me in this, thanks.

  9. Dillon says:

    Update, seemed to just be a permissions issue like you suggested, library is working great now. Thanks again.

  10. Erik says:

    I get this warning:

    Disabling Maintenance mode…

    Warning: Can’t to read the Version header for mdw-event-calendar/mdw-event-calendar.php. The file does not exist. in /XXX/XXX/Sites/mdw-event-calendar/wp-content/plugins/mdw-event-calendar/updater/plugin-update-checker.php on line 277

    And my plugin folder is stuck with .tmp extension.

    For example: my-plugin-folder is my-plugin-folder.tmp

    Any clues on to why?

  11. Jānis Elsts says:

    My psychic debugging skills say that you probably get this error after installing an update, and that your ZIP directory structure is wrong.

    When creating the ZIP file for an update, put all plugin files inside a directory. The directory name should match the plugin slug. Do not put the files at the root of the ZIP archive – it can cause subtle bugs and errors when someone ties to install the update.

  12. Erik says:

    I’ve been digging around and doing all sorts of debugging and I’m guessing that your suggestion is correct, but using your example plugin, I think my ZIP setup is correct. I simply take the plugin folder which is setup like this:


    I ZIP that folder and upload it to my server…am I missing something?

  13. Jānis Elsts says:

    That looks right, but I’d recommend testing it anyway. If you unzip the archive, do you get one folder (plugin-slug-name), or a bunch of files?

  14. Erik says:

    I end up with one folder with the files inside of it. I ran your example as is and it worked fine. So I’m not exactly sure what the issue is.

  15. Jānis Elsts says:

    Hmm. Usually a .tmp suffix indicates some kind of a file-system related problem, and the most common cause of that is ZIP directory structure. However, there are other possibilities as well, like file permissions. For example, does WordPress have write access to the files in your plugin’s directory?

  16. Erik says:

    Yes, checked the permissions and all that. I have had no problems updating other plugins or WP. My only thought is it’s either something on the server I’m downloading it from, or something weird with the way I’m compressing the file.

    I’ve tried a few other updaters, but none seem to be as reliable and straightforward as this one. Just bugged by this .tmp issue.

  17. Erik says:

    Solved: Thanks to some extra help from Janis, we were able to figure out that it was in fact, my archive. I was using the default archiver for Mac and it was not zipping the files into the folder. However, when I used the archive utility to open the ZIP file, it would appear to be correct when in fact it wasn’t.

    While I’m sure you can tweak the settings for the default archiver on a Mac, I downloaded an alternate archiving utility and used that. Worked perfectly.

Leave a Reply