DMSI DDLS – Digital Downloads, Licensing & Subscriptions

2.3.0

New Features
* Every customer you add by hand (Customers > Add New) or with the customer importer now gets a WooCommerce customer account, so they can log in to the customer portal and see their licences and downloads. If a WordPress user with the same email already exists, the customer is linked to that user instead: no second account is made and no password is changed. If no account can be made or linked, the customer is not added and you are told why.
* The option “Email the customer a link to set their password” (ticked by default) sends WooCommerce’s own “New account” email with a link to set a password. A password is never sent by email. Untick it to create the account without emailing the customer.
* The customer Edit screen has a new “Customer Account” box. For a customer who has no account yet, it creates one or links the existing user with the same email, with the same email choice.
* Customers added before this version are left exactly as they were: updating to 2.3.0 sends no email and creates or links no account on its own. A new “WooCommerce Account” column in the customer list shows which customers have no account yet (“No”). For each of them, open Edit and use the “Customer Account” box to create or link the account, with or without the set-password email.

Changes
* A DDLS customer record is now created only by a purchase of a DDLS product (a product with Licensing, Subscriptions or Support turned on, or a Support Plan product), or when you add or import the customer. An order that holds only other WooCommerce products creates no DDLS customer record. Registering on the shop, adding a user in WordPress, editing a profile or opening the customer portal no longer creates one either. A logged-in user who has not bought a DDLS product sees “You have no licenses yet” in the customer portal.
* A customer record is now linked to a WordPress user automatically only when that user has proven the email address is theirs, by following a password reset or “set your password” link sent to that address. Registering with the address, changing to it under My account, logging in or buying with it is no longer enough. A customer who bought before they had an account, or who chose their own password when registering, confirms the address once with “Lost your password”; the customer portal tells them how. You can still link a user yourself on the customer screens.
* A changed account email is copied onto the customer record only after the user has proven the new address in the same way.

Bug Fixes
* The importer now sends the account email before the licence email, and sends both only after the import has been saved, so the “Go to Customer Portal” button in the licence email works when the customer reads it.
* Add New Customer now saves the WordPress User you choose. Until this release the choice was ignored.
* A customer record that is linked to one WordPress user is never shown to a different user who happens to have the same email address.
* A completed order for a product that is not a DDLS product no longer gives the buyer a DDLS support contract and its “Your Support Contract Is Ready” email, and no longer adds that product to the DDLS product list. In an order that also holds a DDLS product, the other products are left alone. Records, support contracts and product list entries made by earlier orders are kept.

2.2.0

New Features
* Subscriptions Pro (version 1.1.2 and later) and Update Server (version 1.0.4 and later) now take their licensing from DDLS itself. The other six DMSI extensions keep their own licensing, and so do earlier versions of these two. Nothing needs to be re-entered and no licence key changes.
* DDLS now keeps a register of the DMSI extensions it knows about, and can tell which of them are genuinely active on the site rather than guessing from what happens to have loaded first. The extension counts on the dashboard widget, and the reminder notice about licences that still need activating, are now correct on sites running many plugins.

Bug Fixes
* Support contract renewals are recorded in the audit log again. Until this release an automatic renewal wrote no record at all, and the safeguard that stops the same contract being renewed twice in one week had nothing to read, so it never fired. Both now work. Contracts that were renewed more than once are not changed by this update.
* Activating the plugin no longer writes a PHP notice to the debug log. The hourly clean-up of unfinished (chunked) file uploads was scheduled too early in the page load, before WordPress had loaded translations; it is now scheduled once WordPress is ready.
* The old DDLS admin page addresses no longer write a “Deprecated: strip_tags()” warning to the debug log on every visit. Those pages now have a title and send you on to the new page before the admin screen starts to draw. Each old address still leads to the same place as before.

Improvements
* A licence can now report how many seats it carries on sites that also run the Team Management extension. Sites without that extension are unaffected.
* Stored credentials are protected with the same encryption everywhere in the DMSI family.
* Tested with WordPress 7.1.

2.1.8

New Features
* Licences now record the edition they were bought as. When a product has variations — Standard, Professional, Trial and so on — the licence remembers which one the customer paid for. This applies everywhere a licence can be created: the admin form, the customer importer, and the API.
* New screen: Licences Without an Edition. A read-only list of every licence on a product with variations that has no edition recorded, so you can find and correct licences created before this version. It changes nothing on its own.

Bug Fixes
* Fixed: on a brand new installation, no licence could be saved at all. The licences table was created without one of the columns the plugin writes to, so every attempt to create a licence failed. New installations now build the table correctly, and any site already affected is repaired automatically when it updates. Sites that were working are unaffected and need no action.

Improvements
* The plugin now asks once — and only once — for a review on WordPress.org. The notice can be dismissed and does not come back.
* Tested with WordPress 7.1.

2.1.7

Bug Fixes
* Fixed email settings save failing with “The dmsilm_email_general options page is not in the allowed options list.” — the email settings option groups (general, queue, logging, notifications, advanced) were only registered when the Email settings page rendered, so the WordPress Settings API save request (options.php) never saw them and rejected every save. The groups are now registered on every admin request.

Improvements
* Email settings page now builds its email/queue/template helper objects lazily, so registering settings no longer instantiates the full email subsystem on unrelated admin requests.

2.1.6

Bug Fixes
* Fixed Action Scheduler group name mismatch — ensure_jobs_scheduled(), trigger_job_now(), and cancel_job() were using the wrong group name (‘dmsi-ddls-digital-downloads-licensing-subscriptions’ instead of ‘dmsi-ddls’), causing the daily self-healing check to create duplicate pending actions on every run
* Added one-time cleanup migration to remove duplicate pending actions accumulated from the bug

Improvements
* Consolidated all 12 Action Scheduler group name references into a single AS_GROUP class constant
* Added action_scheduler_retention_period filter (7 days) to prevent unbounded growth of completed/failed action rows

2.1.5

Bug Fixes
* Fixed variable products showing “Not Licensed” in DDLS Products admin when licensing is enabled on a variation — save_variation_licensing_meta() now re-syncs the parent’s dmsilm_products.requires_license flag based on all child variations

Improvements
* Added variation selector to Add/Edit License admin form — when the selected product is variable, a dropdown of its WC variations is shown so licenses can be bound to a specific variation
* Added variation_id to license save and update flows in admin
* Added variation ownership validation to the activate endpoint — if a license is bound to a specific variation and the client sends a mismatching variation_id, activation is rejected with 403 variation_mismatch