Upgrade
Upgrading Pingen Post takes two steps: overwrite the addon files with the new release, then open Setup → Addon Modules so WHMCS runs the upgrade routine and any database changes are applied.
Always back up your WHMCS files and database before upgrading any module. 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 installation, overwriting the files in:
/modules/addons/pingen
If you use the bundled PDF templates, upload the templates/ folders from the archive as well.
Replace the existing files in place — do not delete the folder first. Your configuration, credentials and send history live in the database, so a file-level overwrite preserves everything.
2. Run the addon upgrade
In your WHMCS admin area, go to Setup → Addon Modules. Visiting the page is enough: WHMCS notices the new version and runs Pingen Post's upgrade routine, which applies any schema changes.
Open Addons → Pingen afterwards and check the Overview tab — the module version shown there should be the one you just uploaded.
Pingen Post also checks its own schema each time its admin page is opened, so an upgrade that skipped Setup → Addon Modules heals itself rather than failing with a database error. Visiting the Addon Modules page is still the tidier route.
Upgrading from 6.x
7.0 replaces the addon's whole admin interface and moves its settings into its own database table. The upgrade is still a file overwrite, but read the Release notes first — they cover what changes for you and what to check afterwards.
Deactivating Pingen Post 6.x drops its database tables, taking your send history and per-client Pingen Post preferences with it. Upgrade by overwriting the files, exactly as described above. (7.0 no longer does this: deactivating it preserves everything — see Uninstall.)
What happens on the first 7.0 run:
- Your 6.x settings — credentials, letter defaults, sending mode, triggers, restrictions, license key — are imported automatically from WHMCS's addon-settings table into Pingen Post's own. The admin area reports how many settings were imported.
- Your send history and per-client preferences are read from the same tables 6.x used, so nothing is lost.
- The stored local license key is deliberately not carried over; the license is re-checked against our server the first time you open the module.
Once you are on 7.0, open Settings and walk through the sub-tabs — 7.0 adds settings that 6.x did not have, and one 6.x setting changed meaning (Send when balance is zero).
Upgrading from 5.x or older
Pingen Post 5.x is the WHMCS 8 release, so this is a WHMCS upgrade as much as a Pingen Post one: move to WHMCS 9 and Pingen Post 6 first, following the 6.0 documentation, then follow this page. Versions 4.x and older used the Pingen Classic API, which is no longer supported; you will need new API credentials — see Pingen Account Configuration.
See the Changelog for the full list of changes in the latest release.