Using the Update Manager to handle updates

Originally published at: Using the Update Manager to handle updates | ClassicPress

Anyone developing a CP-specific plugin needs to be aware that (for now) it’s the developer’s job to process the updates. There are a number of ways to handle this, but the most widely used method is via the Update Manager plugin. This was specifically written for ClassicPress by John Alarcon (Code Potent) after other options…


Thank you for writing about Update Manager.

Tip: if you want to try it on click here to get a temporary installation of ClassicPress, Update Manager and Stats for Update Manager.


Why does this plugin make its own admin page? It seems like it would add to the existing Updates page, so it would all be in one place.

1 Like

The plugin is not for installing updates for your own (meaning: end-user) plugins, themes, or core. That’s what the core Updates page is for. The plugin is for pushing updates out to others, which has nothing to do with the core updates page. On end-users sites, the updates DO appear in their core updates page, right where they belong. The plugin is designed properly and as intended.

1 Like

Oh, okay, but it shows the core transients, so it looked the same to me. That’s a bit confusing.


The Transients view is really more for testing… I wasn’t going to add it for the public release, but, due to popular demand, it was included.

1 Like

@ozfiddler Great write up. One thing that wasn’t mentioned in the post, it also supports themes. So updates can be managed for plugins and themes.


8 posts were split to a new topic: An alternative to CodePotent’s Update Manager