A HostBill update changes application files and may update the database. Plan the update as one controlled change with a usable backup, compatible integrations and a clear test of billing, provisioning and support afterwards.
IN THIS ARTICLE
01 Prepare the change
Read the release instructions for your target build and confirm PHP, ionCube and module compatibility. Record custom templates, hooks and any renamed administrator directory. Choose a maintenance window that accounts for payment callbacks, order activity and scheduled jobs.
Back up the database, application files, private attachments and configuration, including the original encryption hash. Verify that the backup can be read and restored. HostBill's update procedure does not create this backup for you.
02 Apply and test the update
- Prevent concurrent administrative changes and pause scheduled work as required by your maintenance plan. Record pending transactions and tasks so they can be reconciled afterwards.
- Download the release from your authenticated HostBill portal. Upload the new application files while preserving the existing
includes/config.php. - If you use a custom administrator folder, place the package's new administrator files into that folder. Do not leave the active administrator interface running older files.
- Open the installation address followed by
/install/and complete the upgrade workflow. Investigate an incomplete upgrade before attempting unrelated configuration changes. - Remove the installation directory after success. Reapply reviewed customisations against the new templates, rather than restoring old template files wholesale.
- Test staff and client login, checkout, a controlled invoice/payment workflow, support attachments and a representative module action. Resume cron and queue processing, then review failures and delayed callbacks.
Common questions
Why are new administrator features missing after a successful upgrade?
A renamed administrator directory may still contain the previous template files. Compare the deployed files with the downloaded package and update the active directory identified by the configuration.
Can I downgrade by copying the old PHP files back?
Do not assume that is sufficient after database changes. Recovery may require a matching database and file backup. Before restoring, account for payments or customer activity received since the backup so they are not lost or processed twice.