WP Plugin Update Server

Screenshots

WP Plugin Update Server allows developers to provide updates for plugins and themes packages not hosted on wordpress.org. It is useful to provide updates for plugins or themes not compliant with the GPLv2 (or later). Packages may be either uploaded directly, or hosted in a remote repository, public or private. It supports Bitbucket, Github and Gitlab, as well as self-hosted installations of Gitlab. Package updates may require a license, and licenses can be managed through an API or a user interface within WP Plugin Update Server. Important notes This plugin is for developers only. Zip PHP extension is required (use ZipArchive, no fallback to PclZip). For more information, available APIs, functions, actions and filters, see the plugin’s full documentation. Make sure to read the full documentation and the content of the “Help” tab under “WP Plugin Update Server” settings before opening an issue or contacting the author. Overview This plugin adds the following major features to WordPress: WP Plugin Update Server admin page: to manage the list of packages and configure the plugin. Package management: to manage update packages, showing a listing with Package Name, Version, Type, File Name, Size, Last Modified and License Status ; includes bulk operations to delete, download and change the license status, and the ability to delete all the packages. Add Packages: Upload update packages from a local machine to the server, or download them to the server from a remote repository. General settings: for archive files download size, cache, and logs, with force clean. Packages licensing: Prevent plugins and themes installed on remote WordPress installation from being updated without a valid license. Licenses are generated automatically by default and the values are unguessable (it is recommended to keep the default). When checking the validity of licenses an extra license signature is also checked to prevent the use of a license on more than the configured allowed domains. Packages remote source: WP Plugin Update Server can act as a proxy and will help you to connect your clients with your plugins and themes kept on a remote repository, so that they are always up to date. Supports Bitbucket, Github and Gitlab, as well as self-hosted installations of Gitlab. Packages will not be installed on your server, only transferred to the clients whenever they request them. To connect their plugins or themes and WP Plugin Update Server, developers can find integration examples in the wp-plugin-update-server/integration-examples directory, or check the documentation of the WP Package Updater. In addition, a Must Use Plugin developers can add to the WordPress installation running WP Plugin Update Server is available in wp-plugin-update-server/optimisation/wppus-endpoint-optimizer.php. Upgrade Information When upgrading from v1.3, licenses from Software License Manager plugin will be migrated automatically, and SLM will be bypassed while doing license checks using the old API, and compatibility will be ensured until v2.0. It is recommended to dactivate or uninstall Software license Manager entirely. Developers will need to update the WP Package Updater library before v2.0 as support for SLM API calls will be removed then. Roadmap Aside from minor version updates (bugfixes, interface improvements and simple new features), below is the current roadmap. This can evolve depending on feedback, reviews and popularity. v1.5: Add statistics for packages passing through WP Plugin Update Server – number of updates, number of installs, etc for each package – potentially with CSV export. v1.6: Optionally include the WP Package Updater and its logic to packages passing through WP Plugin Update Server (has to be done manually in version prior to 1.6, which may potentially lead to errors if not done properly). This feature would be enabled only on an opt-in basis. Special Thanks A warm thank you to Yahnis Elsts, the author of Plugin Update Checker and WP Update Server libraries, without whom the creation of this plugin would not have been possible. Authorisation to use these libraries freely provided relevant licenses are included has been graciously granted here.