Upgrade
Upgrading Pingen Post takes two steps: overwrite the plugin files with the new release, then run the upgrade from the Blesta Plugins page so any database changes are applied.
Always back up your Blesta files and database before upgrading any plugin. If something goes wrong, a clean restore is much faster than troubleshooting a half-applied upgrade.
1. Replace the files
Upload the contents of the new release archive over your existing Pingen Post installation, overwriting the files in:
/plugins/pingen
Replace the existing files in place — do not delete the folder first. Blesta keeps configuration in the database, so a file-level overwrite preserves your credentials, letter defaults, and everything you have already sent.
2. Run the plugin upgrade
In your Blesta admin area, navigate to Settings → Plugins and open the Installed tab.
If the new version requires a database migration, an Upgrade button will appear on the Pingen row. Click it to apply the upgrade.
If no Upgrade button is shown, the new files are all that was needed and you're done.
Coming from the WHMCS module?
Pingen Post for Blesta is a separate product from the WHMCS addon. There is no in-place migration between the two platforms — install the Blesta plugin fresh, then re-enter your Pingen API credentials as described in Pingen Account Configuration. Your Pingen account, credits, and sent letters live on Pingen's side and are unaffected.
See the Changelog for the full list of changes in the latest release.