Black Friday
Skip to documentation content

Hotel Setup

Configure managed hotel Pages

Assign Rooms, Booking, Contact and My booking Pages while preserving content, access settings and deliberate unassignment.

Assign native WordPress Pages to hotel entry points without replacing their content, status or your homepage. Initial setup can create/reuse an eligible Page; later deletion and deliberate unassignment require an explicit operator choice.

Page roles

Role Setup screen Supported shortcode Public behavior
Rooms Hotel Booking → Settings → Rooms page [kimorapro_hb_rooms] Mapped catalogue plus a contract-controlled /rooms/ fallback
Booking Hotel Booking → Settings → Booking page [kimorapro_hb_booking] Public mapped Page; no virtual Booking Page replacement
Contact Hotel Booking → Newsletter & Contact → Contact page [kimorapro_hb_contact] Public mapped Page; intake/recipient/privacy readiness remains separate
My booking Hotel Booking → My booking page, in Pro [hotel_booking_account]; alias [hotel_booking_customer_dashboard] Public mapped Page; account navigation/rendering also needs its feature

Use an administrator with the required hotel settings and WordPress Page editing/publishing permissions. Private Pages require their native read permission. Setup does not grant a Pro or theme license.

Choose or repair an assignment

  1. Open the role’s setup screen and read the assigned Page/status and readiness message.
  2. Open the existing Page in WordPress and confirm its content and publication/access settings.
  3. For Free Pages, use Search pages, select the appropriate assignment and Save page assignment.
  4. For Pro My booking, use Search Pages, choose the WordPress Page, then Assign Page.
  5. Add the role’s shortcode in the Page editor if it is missing, then publish the intended Page through WordPress.
  6. Return to the setup screen and use its public view link; verify the expected form/catalogue/account state.

Choosing a Page does not add a shortcode or change its title, slug, status or template. Do not assign one Page to conflicting roles. A page builder can render a shortcode outside the content inspected by readiness checks; inspect the actual public output.

Missing, renamed and deliberately cleared Pages

  • Renamed: the mapping follows the Page ID/permalink. Check the generated URL and update your own manually configured links/menu items where needed.
  • Trashed/deleted: restore through WordPress, choose another eligible Page or use the explicit replacement action offered by that role. Ordinary visits do not silently recreate it.
  • Deliberately unassigned: keep that choice until you assign again. For Pro use Clear assignment; Free’s selector includes No assigned page.
  • Pending/failed setup: use the role’s retry action when offered. Multiple candidates or uncertain provenance require explicit review, not repeated activation.
  • Hidden/private/password-protected: public navigation does not treat it as an open entry point. Decide the intended access in WordPress rather than relying on fallback.

Rooms has limited fallback behavior described in route semantics. Do not apply that assumption to the other Page roles. Pro account setup can produce an unavailable Page before licensing; this is different from a missing Page.

Recovery

Record the Page ID, role, status and redacted URL before changing an assignment. Restore the prior mapping/content through the owning screen if the result is wrong. Avoid deleting Pages, changing Reading settings or importing a demo as a repair. Verification must include the public view, not just a saved assignment notice.

Was this article helpful?

Your feedback helps us improve the documentation.