Upgrade the module as a complete release and verify the workflows your business uses afterward. Back up the database and current files first, because module records, email customizations and application policies are part of the operating configuration.
IN THIS ARTICLE
01 Prepare the update
- Read the release notes for the target package and confirm its WHMCS, PHP and provider requirements.
- Check both web and cron PHP environments. The module's supported PHP list does not override the requirements of WHMCS, gateways or your theme.
- Review unresolved renewals, application setup, trials and queued notifications so you can recognize pre-existing problems after the update.
- Create a verified database and file backup, including the installed module, hooks, templates and your configuration.
- Test the package on a controlled copy with external charges, provisioning and customer emails appropriately isolated.
02 Install the complete release
Upload the release files over their matching locations, preserving the supplied directory structure. Include the addon, server module, trial gateway and both hook files where supplied. Do not update only the visible administrator assets while leaving old backend or hook files in place.
Open Addons > Nabtech Hosting Suite so the module can apply its supported schema updates. Check the environment and version display and resolve reported migration errors before allowing normal administration to continue.
03 Review current product behaviour
Recent versions expanded application customer tools, AI-credit and lifecycle messages, client-area dropdown styling and inside-card corner behaviour. Review older non-WordPress application tool settings and save your intended profile explicitly.
Test the active WHMCS theme, checkout, website portal and representative product managers. Review built-in email previews and separately inspect customized templates, which are preserved instead of overwritten.
04 Verify operations
Confirm cron completion, a harmless provider read, a test application setup, an AI test where enabled and the relevant renewal invoice workflow. The supplied renewal accounting implementation requires WHMCS 8; do not combine a module update with an unsupported billing-platform major-version change.
Check current service dates, credit balances and open operations against your pre-update record. Broaden testing only when a changed component or an observed problem requires it.
What should I do if a Hosting Suite update fails?
Preserve the error and stop repeated partial uploads. Determine whether files, schema changes or an external dependency failed. Restore files and database together according to the prepared recovery plan when rollback is necessary. Reverting only PHP files after a schema change may not produce a compatible installation.
05 Keep the rollback decision concrete
Define which failure would require restoring the previous installation and which can be corrected without rollback. Preserve the pre-update backup until critical billing and provisioning workflows have passed. A successful administrator login is only one check and does not demonstrate that invoice events or scheduled jobs still run.
If the release changes customer presentation, inspect an existing service as well as a new order. Existing plans can carry older saved policies that a newly created product does not reproduce. Record any deliberate configuration edits made during validation, since restoring an earlier database will also restore the earlier settings. Keep the customer-facing support instructions aligned with the version you ultimately retain.