Use Self Update to install an available update on a website already running Fusion Core. Moving an older DHRU Fusion website to Core uses the legacy upgrade procedure.
Before updating
- Choose a maintenance window. Tell other administrators to avoid changing the site while the update runs.
- Make a recent, restorable backup of the database and site files. Include
DhruFusionCore/config/.env, private storage, uploads, custom themes, and modules. - Check free disk space and the system requirements. Automatic updates need PHP ZIP and outbound HTTPS access.
- Confirm that your Fusion Core service is eligible for updates in your Dhru account.
- Sign in to the website's Admin panel with a Full Access administrator. Complete the account's two-factor authentication if enabled.
Keep the .env backup secure. Its encryption key is needed to read stored supplier and payment credentials; restoring only the database will not replace that key.
Check the available update
Open Self Update in Admin. The page checks for an update when opened; use Check for updates to check again.
Review the installed version, available version, and What's new. The updater offers releases that are available for your installation. A release announced elsewhere may not yet be offered for your current version or service.
You're up to date means the check completed and no newer eligible release was offered. Couldn't check for updates means the check failed; it is not confirmation that your site is current.
Choose the database backup option
Keep Automatic backup (recommended) selected unless you already have a recent database backup and know how to restore it.
If you choose I'll use my own backup, confirm that you have a recent database backup and can restore it. Fusion Core will skip creating a database backup for that update. Its automatic file backup does not replace a database backup or your own full-site backup.
Choose the backup option again for each new update or repair attempt. A backup taken while the website is changing may not represent one consistent point in time; coordinate your maintenance window and any external jobs accordingly.
Run the update
Select Update now once, then keep the page open. Fusion Core downloads and verifies the official package, prepares the update, applies its changes, and checks completion. The website can show a maintenance notice while this happens.
Do not upload another package, edit application files, or start a second update while the current one is in progress. Avoid changing scheduled tasks or running external maintenance against the database during the update.
Wait for Update complete. Refresh Admin and confirm the installed version, then check the storefront, sign-in, automation status, and your important supplier and payment workflows.
If the connection is interrupted
Return to Self Update. If the page offers Continue update, use it to resume the recorded attempt. If sign-in is required, sign in again with the same Full Access administrator and return to the update page.
If the page offers Try again, use it to reconnect or recheck the recorded state. It does not mean you should upload the package again.
If the update reports a failure, follow the action offered on that page. Cancel update is available only when the updater considers cancellation safe. For a changed release, cancel when offered, then check again.
If no safe continuation or cancellation is offered, leave the files and database in place and contact DHRU Support with the update reference and available report. Do not delete update records, change migration history, or disable verification to force another run.
Repair and recovery
Reapply latest patch, when available, is a repair action. It is not a way to undo database changes or return to an older release. Use it for an appropriate repair or when directed by support, with a current backup.
If a complete restore is necessary, the database and site files must come from a matching backup. Replacing the application with an older ZIP does not reverse database upgrades. Have your hosting provider or support review the restore before reopening the website.
Older installations or damaged update screens may need the official full-package update route through /setup/. Ask support for the correct package and steps for that installed version; do not run a fresh installation over it.