PQM Pro – Aktualizacje, Licencja i Bezpieczeństwo
PQM Pro – Aktualizacje, Licencja i Bezpieczeństwo
PQM Pro and its modules can be updated from a dedicated update server. This allows customers to receive new versions and fixes without manually uploading ZIP packages, while access to updates can be controlled by license entitlements.
How updates work
WordPress has a built-in plugin update system. PQM Pro can integrate with that system through a custom updater. This allows PQM Pro and its modules to behave like standard WordPress plugins even when update packages are delivered from an external server.
Where updates appear
- Plugins screen,
- Dashboard → Updates,
- PQM → Modules for module updates,
- version details or changelog screen if provided.
PQM Pro updates
The main PQM Pro plugin should have its own version check. The system compares the installed version with the latest version available on the update server. If a newer version exists and the license allows access, WordPress displays the update.
Module updates
Modules should update like normal WordPress plugins. The difference is that version information and package URLs come from the PQM update server. The PQM → Modules screen can show an Update button, but the actual update should use WordPress plugin update functions.
License
A license defines whether an installation has access to PQM Pro and specific modules. A typical license record may include:
- license key,
- status: active, expired or blocked,
- domain or activation count,
- plan,
- list of enabled modules,
- expiration date for updates or support.
Entitlements
Entitlements define which modules or features belong to a license. A customer may have PQM Pro plus NASA+ Analytics and Orders, but not Warehouse or Communication.
{
"license_status": "active",
"plan": "pro",
"modules": [
"pqm-nasa-analytics",
"pqm-orders"
]
}Secure update packages
Update packages should be downloaded from a trusted secure endpoint and only when the license allows access. Package URLs may be temporary, tokenized or generated on request.
Before updating
- Create a full backup of files and database.
- Check WordPress and PHP requirements.
- For major updates, test on staging first.
- Update PQM Pro before updating modules.
- After updating, test tasks, reports, email automation and the customer panel.
Common update issues
| Issue | Possible reason | Solution |
|---|---|---|
| Update not visible | WordPress update transient cache. | Check updates again or clear the update_plugins transient. |
| Missing update icon | The custom updater does not pass the icons field. | Add icons to update and no_update responses. |
| Package cannot be downloaded | Expired license or invalid package URL. | Check license status and generate a new secure URL. |
| Module fails after update | Requires a newer PQM version. | Update the main PQM plugin first. |
| Critical error | PHP conflict, missing file or incompatible version. | Restore backup and check logs. |
Security best practices
- Install module packages only from trusted sources.
- Do not share license keys publicly.
- Do not update production without a backup.
- Keep WordPress, PHP and plugins up to date.
- Check error logs after updates.
- Use staging for larger changes.
A well-designed updater makes PQM Pro feel like a professional WordPress product: updates are visible, convenient and controlled by license access.