WBAMS updates itself from the control panel, checks every file it downloads, and keeps a copy of what it replaces so a failed update puts things back.
How you hear about a release
WBAMS checks for a new release every eight hours (with the scheduler running) and whenever someone presses Check Now on Update WBAMS. Administrators allowed to update get one email per release and see it in the notifications bell.
Before you press Update
- Read the release notes
For the new release and every release you are skipping. Manual steps are always listed first.
- Back up
The database and the files together, including
settings.phpand the encryption hash. - Update
Open Utilities › Update WBAMS and apply the update. Let the database step finish.
- Check
Sign in and open one page from each area: billing, support, the website.
What the updater does
- Downloads the package with an expiring token and checks it against the published SHA-256, then every file against the package's own manifest. A package without its checksum list is refused.
- Copies every file it replaces aside first; a failure part way restores them and removes what it added.
- Runs one update at a time. A second start while one is running is turned away.
- Cleans up its download afterwards and keeps one rollback copy of the files the latest update replaced.
From the command line
php upgrade.php is the route for when the browser update has failed.
Full guide
The complete reference is Updates, backups, and recovery in the WBAMS documentation.