Install and activate like any other plugin.

Navigate to Dashboard > Plugins > Manage CP Plugins and start managing ClassicPress Plugins. You can install, activate, deactivate, update, delete, and also search Plugins all from within the same screen. The results are cached locally for fast performance, and you can refresh the local cache on the click of a button.

It has a pagination and a total plugins display to navigate (15 plugins a time) through the assets. A “more info” will display all information known to ClassicPress about the plugin and developer.

The plugin requires wpremoteget and fileputcontents to work properly on the server.

Plugins not listed in the ClassicPress Directory

It is possible to manage plugins that are not listed in the ClassicPress Directory with this plugin as well. The conditions for this to work are:

  • the GitHub stored Plugin MUST have a tag classicpress-plugin.
  • the GitHub Repository MUST have a valid Release tag named with a SemVer

release version (like 1.0.0) .
- the release MUST have a manually uploaded Zip Asset uploaded to the release section for Attach binaries by dropping them here or selecting them. holding the plugin.
- the repository MUST have EITHER OR BOTH a readme.txt OR (can be all uppercase too). The readme.txt is prioritized and MUST follow the WordPress readme.txt rules. The file is used only as backup, and if used, MUST have at least one line featuring # Plugin Name Here.
- the repository MUST be public.

By default, there is a vetted list of Organizations added to the plugin. If a Developer wants to appear on said list, they can submit a PR to the github-orgs.txt File of this Plugin, by adding their Guthub Organization data to the JSON array. The Organization AND the PR initiator will be reviewed both by the author of this plugin as well the ClassicPress Plugin Review Team. Only after careful assessment the Developer will be added to the Verified List of Organizations, and thus appear pre-selected in the Repositories queried by this plugin.

Other, non verified Repositories (both users and orgs) can still be added easily by an end user in the dedicated Settings page (Dashboard > Settings > Manage CP Repos).


  • The plugin does not take any responsibility for Plugins downloaded from the ClassicPress Directory or GitHub, not even if verified Organization’s software.
  • The ClassicPress Plugin Repository is not always well maintained by the Developers who list their plugins. They forget often to bump the Version Number of their Plugins. This means, you might not see an update, even if there is one, or you might see an update to a certain version and get an update to a much higher version.
  • If a GitHub stored plugin is not following above (MUST) clauses, it will not be possible for this plugin to find, pull or else manage such repos.
  • If you run into GitHub API Limits (it is not so generous) you should create a Personal Authentication Token as shown here_. You should only give this Token “read” rights, no post or edit rights. You should never share this Token with anyone. You should then store this Token on the setting for it under Dashboard > Settings > Manage CP Repos. This will bump your GitHub API limits to 5000 per hours (which is far enough).

Search results