Core’s public catalog defines which template identities and exact versions a theme can override. Copy the current supported template surface, not a private partial, controller, email, invoice or repository.
Use kimorapro_hb_template_override_catalog() and kimorapro_hb_template_override_statuses() for class-free diagnostics. The internal TemplateResolver implementation is not a callable theme API.
Paths and required metadata
Core templates use hotel-booking/{logical-template}.php; Pro templates use hotel-booking/pro/{logical-template}.php. The template package ID remains hotel-booking even though Free’s plugin folder is kimorapro-hotel-booking.
A confirmation wrapper for the current catalog has this metadata and prepared slot:
/*
Hotel Booking Template: frontend/booking/confirmation
Template Package: hotel-booking
Template Version: 1.2.0
Theme Contract: 1.12.0
*/
defined('ABSPATH') || exit;
echo $confirmationHtml;
The owner supplies authorized prepared HTML; never substitute request input or instantiate a private receipt presenter. Match the slot’s actual payload rather than assuming every template receives a raw Booking model.
Current key versions
Book Now and confirmation are 1.2.0; booking index is 1.3.0; room detail is 1.5.0. Pro customer detail is 1.1.0 and customer cancellation 1.2.0. Contact form, newsletter form and Search have their own catalog entries; use the runtime catalog rather than an older manifest’s incomplete list.
The exact template version must match. The declared Theme Contract major must be compatible and not newer than the active contract. Child → parent → plugin resolution skips rejected candidates instead of forcing stale payloads into them.
Keep hooks, validation fields, access markers and owner-provided action URLs intact. A version header is not permission to copy business logic. After any Core/Pro update, review rejected overrides, then test the native fallback and the intended theme/child pair independently.
See child-theme safety.
