Upgrade a reseller connector from an eligible published release while keeping a recoverable record of the current installation. The package version, target platform, generated module name and release documentation should remain together.
IN THIS ARTICLE
01 Prepare the change
- Read the new publication's version, platform, release notes and compatibility requirements.
- Download the artifact through the current grant workflow and verify its digest.
- Back up the billing installation, database and connector configuration according to the platform's normal recovery process.
- Preserve the existing connector package and record where credentials are stored. HostBill and FOSSBilling can rely on process environment values; Blesta stores encrypted module-row secrets; WHMCS uses saved registrar configuration.
- Review any changed field mapping, API behaviour, pricing import or required PHP dependency before overlaying files.
02 Install and verify
Keep the generated module folder and discovery filenames unchanged. A rename can cause the host to treat the connector as a different module and leave existing domain assignments behind.
After installation, test a read-only account request, an owned domain and the normal scheduled environment. Review TLD pricing with a preview before allowing any price-writing job. Exercise the representative native workflow that the release changed, including its pending and error states.
Confirm existing orders still reference the same upstream operations. An upgrade should not create new business requests merely because a local cache or setting was reset.
Common questions
Does a published ZIP mean every platform version was tested?
No. Publication and artifact integrity establish release identity. Native acceptance depends on the installed billing-platform and PHP versions and the workflows you enable.
Can I roll back just the PHP files?
Follow the release's migration notes and platform recovery plan. If configuration or schema changed, a file-only rollback may not restore a compatible state.
Does withdrawal remove an already installed connector?
No. It stops future eligible downloads and invalidates outstanding grants. Existing installations require a coordinated update or retirement process.
Should I put credentials inside my archived ZIP?
Keep package code separate from secrets. Preserve protected configuration through the platform's appropriate backup mechanism and restrict access to that backup.