Download the PHP package shazzad/plugin-updater without Composer

On this page you can find all versions of the php package shazzad/plugin-updater. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of shazzad/plugin-updater

Informations about the package plugin-updater

WordPress Plugin Updater Package

A comprehensive WordPress plugin updater library that enables automatic updates, license verification, and remote plugin management for custom WordPress plugins.

Features

Requirements

Installation

Which namespace to use

The library ships one namespace per major version, side by side:

The majors never share classes, so plugins on different library versions coexist on one site without the first-loader-wins fatal V1 was exposed to.

The namespace number matches the server API it calls: V4 talks to wp-repo/v4, and a future V5 would talk to wp-repo/v5. The one exception is legacy: V1 and V2 both call wp-repo/v3 (V3 was never released under that name — it became V4 before shipping).

Namespace Status Server API Guide
Shazzad\PluginUpdater\V4 Active wp-repo/v4 (plugins/{uid}) docs/v4.md
Shazzad\PluginUpdater\V2 Stable, additive fixes only wp-repo/v3 (products/{id}, legacy exception) docs/v2.md
Shazzad\PluginUpdater (V1) Frozen, critical fixes only wp-repo/v3 (products/{id}) docs/v1-legacy.md

Minimal example (V4, commercial plugin)

The free-plugin (V4\Insights) quick start, every config key, and what happens without a product_uid or with a wp-repo/v3 api_url are in the V4 guide.

Documentation

The rest of this page applies to every version.

Server responses

Your API server should provide updates, details and check_license endpoints (plus ping for V1/V2 or the Insights track / optout routes for V4). They return the same bodies on wp-repo/v3 (V1, V2: /products/{product_id}/…) and wp-repo/v4 (V4: /plugins/{uid}/…). Each version's paths are in its guide; the full v4 contract is docs/v4-api.md in shazzad/plugin-repo.

Update check

Plugin details

License verification

The renewal_url field is optional in the license verification response. When present and the license status is expired, a renewal link is displayed on the admin license page. The URL supports two placeholders that are replaced automatically:

A static URL without placeholders (e.g., https://example.com/renew) is also supported.

Request parameters

API requests to updates, details, and check_license include these query parameters:

Custom metadata

Every version accepts plugin metadata through setMeta() (static values or closures) and setMetaCallback() (one callback that builds the whole array); V2 and V4 also take them as the meta / meta_callback config keys. V1 and V2 send it with each ping, V4 with each Insights track.

WordPress update hooks

The Updater of V1, V2 and commercial V4 integrates with the WordPress core update system using these hooks:

Activation/deactivation hooks, admin notices and scheduled tasks differ per version; each guide lists its own.

License admin page

When licensing is enabled, the updater adds an admin page with:

By default, the license page appears under the Plugins menu; an empty parent falls back to plugins.php. The page is always a submenu (add_submenu_page()) — there is no top-level option. To customise the parent, use the menu key in V2 and V4, or the $menu_parent constructor argument in V1.

Security Features

Error Handling

The updater includes comprehensive error handling:

Errors are returned as WP_Error from the Client methods and surfaced on the license admin page; the library does not write to the PHP error log.

Changelog

See CHANGELOG.md for the full release history.

Support

For support and bug reports, please contact your plugin developer or visit the plugin's official support channels.

License

This updater package is typically licensed under the same terms as your main plugin. Check your plugin's license file for specific terms.

All versions of plugin-updater with dependencies

PHP Build Version
Package Version
Requires php Version >=7.4
ext-json Version *
ext-curl Version *
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package shazzad/plugin-updater contains the following files

Loading the files please wait ...