Black Friday
Skip to documentation content

Aurelia Theme

Update Aurelia and plan a safe rollback

A theme update replaces presentation/runtime files; it does not reverse Core/Pro schema, booking, financial, privacy or external-provider history. Retain the previous complete parent package and a reviewed recovery plan before replacement.

A theme update replaces presentation/runtime files; it does not reverse Core/Pro schema, booking, financial, privacy or external-provider history. Retain the previous complete parent package and a reviewed recovery plan before replacement.

Check the installed downloader first

Use the intended Aurelia product/stylesheet aurelia-theme and current license/update controls. Verify the package offer, version, permitted origin, size, SHA-256 and archive root through the supported updater. Do not bypass TLS, ticket or integrity checks.

Current 1.3.7 release notes describe a streamed-download metadata/size-check fix. A fix inside the new ZIP cannot repair the older downloader currently running; an affected installation can need the owner’s approved one-time hotfix or manual WordPress theme replacement. Do not rebuild or overwrite an immutable published version to conceal a delivery problem.

Rehearse replacement

  1. Back up files/database and capture exact parent/child/Core/Pro versions, customizations and current data state.
  2. Test the approved package on an isolated copy without real mail, gateway, OTA or license mutations.
  3. Review child overrides and their exact template versions, then perform the intended supported update/replacement.
  4. Read back the installed version and check layout, assets, forms and authorized booking/account surfaces.

The theme’s general Core requirement and optional sample-hotel import minimum differ. An update must not silently run a new demo import to repair an existing site’s layout.

Roll back the correct scope

Restore the previous complete compatible parent package when a code rollback is appropriate, preserving child files and operational data. Check cache/worker behavior and rejected overrides afterward. Do not restore an old database indiscriminately: it can lose new bookings or reintroduce erased information.

The current shared theme client separates runtime proof from renewal/update permission and may lock paid presentation when proof is unavailable/denied. Copying license storage is not a rebind. Actual server activation, download delivery and licensed frontend recovery require separate environment evidence.

See child-theme safety and backup/incident response.

Was this article helpful?

Your feedback helps us improve the documentation.