Publishing a Version with Update Server #
Publishing a version with the extension active triggers additional behaviors beyond core DDLS.
What This Extension Adds #
Core DDLS publishing makes a version visible in the customer portal. With DMSI Update Server, publishing also triggers email notifications to license holders (if enabled) and makes the version available to client software via the REST API.
What Happens When You Publish #
| Step | Core DDLS | With Update Server |
|---|---|---|
| 1 | Version becomes visible in customer portal | Same |
| 2 | Download counter starts | Same |
| 3 | (nothing) | If "Send Email Notification" is checked AND global email is enabled: queues emails for all active license holders |
| 4 | (nothing) | Version becomes available via REST API update checks for eligible licenses |
| 5 | (nothing) | Version meta defaults initialized (channel, rollout) if not already set |
Email Notification on Publish #
If you checked "Send Email Notification" on the version edit form:
- On publish, all active licenses for this product are queried
- One email is queued per license holder in
wp_dmsilm_us_email_queue - Emails are processed in batches every 15 minutes by the background cron job
- Email includes: version number, changelog, and a download link (if configured)
- Failed emails retry up to 3 times
Note: Email queuing happens at publish time. If you uncheck "Send Email" after publishing, emails already queued continue to send.
API Availability After Publish #
After publishing:
- Clients calling the update check endpoint receive this version if eligible (correct channel, within rollout, environment compatible)
- Clients calling the versions list endpoint see this version
- The version appears in the customer portal's Available Updates page
Best Practice: Configure Before Publishing #
Configure all Update Server Settings before publishing, not after:
- Set channel, rollout, file, and compatibility before clicking Publish
- Changing rollout after publish is fine (and expected for staged releases)
- Replacing the file after publish is possible but not recommended