Skip to main content

PBJ License Manager Changelog (v1.1.0): Packages Tab and Emailed Download Links

PBJ License Manager turns any WordPress site into a license server for plugins and themes you sell: issue keys, track per-key site activations, serve WordPress-native update manifests to valid keys, and sign download links so package URLs can’t be shared. A bad key or an unreachable server never breaks a customer’s plugin — it only means no update is offered. Here’s the release history.

Version 1.1.0

  • Packages tab. Upload, store, and delete plugin zips per product in a deny-all protected uploads folder; “Make current” updates the manifest and latest version in one step.
  • Download links in key emails. A new {download_url} placeholder puts a signed link (72-hour default, configurable) to the current release of the purchased major version right in the key email. Feature updates still flow through WordPress updates only.
  • “Resend email” action on each key, regenerating a fresh download link.
  • New email-link-lifetime setting; schema v2 migration upgrades default email templates in place; opt-in uninstall data delete now also removes stored package files.

Version 1.0.0

  • Products registry — register each plugin or theme you sell, with a per-product site-activation limit and current major version.
  • Four ways to issue keys: manually from the admin, via a PHP hook, via an authenticated REST endpoint, or automatically from paid PBJ Form Builder submissions.
  • Key-aware update manifests — customers with a valid key get update packages; everyone else keeps a fully working plugin but receives no downloads.
  • Signed, expiring downloads — package URLs carry an HMAC token so they can’t be shared.
  • Key delivery emails, per-key site activations, CSV export, a built-in User Guide and Feedback tab, and a bundled GPL client SDK to drop into the plugins you sell.
July 4, 2026

PBJ License Manager turns any WordPress site into a license server for plugins and themes you sell: issue keys, track per-key site activations, serve WordPress-native update manifests to valid keys, and sign download links so package URLs can’t be shared. A bad key or an unreachable server never breaks a customer’s plugin — it only means no update is offered. Here’s the release history.

Version 1.1.0

  • Packages tab. Upload, store, and delete plugin zips per product in a deny-all protected uploads folder; “Make current” updates the manifest and latest version in one step.
  • Download links in key emails. A new {download_url} placeholder puts a signed link (72-hour default, configurable) to the current release of the purchased major version right in the key email. Feature updates still flow through WordPress updates only.
  • “Resend email” action on each key, regenerating a fresh download link.
  • New email-link-lifetime setting; schema v2 migration upgrades default email templates in place; opt-in uninstall data delete now also removes stored package files.

Version 1.0.0

  • Products registry — register each plugin or theme you sell, with a per-product site-activation limit and current major version.
  • Four ways to issue keys: manually from the admin, via a PHP hook, via an authenticated REST endpoint, or automatically from paid PBJ Form Builder submissions.
  • Key-aware update manifests — customers with a valid key get update packages; everyone else keeps a fully working plugin but receives no downloads.
  • Signed, expiring downloads — package URLs carry an HMAC token so they can’t be shared.
  • Key delivery emails, per-key site activations, CSV export, a built-in User Guide and Feedback tab, and a bundled GPL client SDK to drop into the plugins you sell.

Latest Articles