Skip to documentation content

Getting Started

Upgrade and roll back the release set

Update Hotel Booking Free, Pro and Aurelia in a safe order while preserving data and maintaining a tested rollback path.

Update the release set in dependency order: Hotel Booking Free, Hotel Booking Pro, then Aurelia. Preserve the database and installed directories until the post-update booking smoke test passes.

Before you begin

Create a complete database backup and copies of the current Free, Pro and theme directories. Record current package versions, license status, active theme, menus, widgets, homepage, permalinks, locale and multilingual configuration. Keep the rollback ZIPs outside the web root.

Update Free and Pro

  1. Put the public booking journey into the site’s normal maintenance state.
  2. Update Hotel Booking Free to the target version.
  3. Confirm Free remains active and Hotel Booking → Settings loads.
  4. Update Hotel Booking Pro to its compatible target version.
  5. Confirm Pro remains active and open Hotel Booking → License.
  6. Select Check now, then confirm the expected feature and update status.

For a manual replacement, replace only the specific plugin directory from a trusted ZIP. Do not merge old and new files. On a bind-mounted or bytecode-cached environment, reload PHP workers after replacement.

Update Aurelia

The supported path depends on the installed version:

  • From Aurelia 1.0.7 to 1.1.0-rc.8, use manual ZIP replacement because 1.0.7 predates the external updater adapter.
  • From 1.1.0-rc.7 to 1.1.0-rc.8, use the native WordPress update offered by Aurelia’s external updater, or perform an equivalent exact ZIP replacement.

An Aurelia update has no database migration. It must preserve theme mods, widgets, menus, the selected homepage, permalinks, locale, multilingual data, Hotel Booking schemas, plugin directories and translations.

Clear stale runtime state

  1. Reload PHP workers when the host uses OPcache or an equivalent bytecode cache.
  2. Flush the persistent object cache when configured.
  3. Purge or bypass full-page and CDN caches for the verification paths.
  4. Use a private browser session for the first real HTTP smoke test.

Verify the update

Confirm the installed versions, then test:

  1. WordPress administration and the Hotel Booking dashboard.
  2. /rooms/ and /search-availability/ through real HTTP requests.
  3. One availability search with dates and guests.
  4. One complete booking using a safe test payment method.
  5. The confirmation view and saved price, payment and tax snapshot.
  6. Pro license status and one required Pro workflow.
  7. Aurelia desktop and mobile navigation when the theme is active.

Roll back

If a critical check fails, stop new bookings. Deactivate Pro first when rolling back the Free/Pro pair, restore the previous Free and Pro directories, restore the database only when the update changed it incompatibly, then reactivate Free before Pro. For Aurelia 1.1.0-rc.8 to 1.0.7, use manual ZIP replacement and reactivate the prior theme version.

Clear the same caches and repeat the real HTTP smoke test. A successful rollback preserves bookings, payments, tax snapshots, room policies, customers, license state, iCal sources and external inventory blocks.

Was this article helpful?

Your feedback helps us improve the documentation.