Black Friday
Skip to documentation content

Developer Reference

Respect Core, Pro and theme ownership

Core owns the shared booking domain and public presentation boundary; Pro owns optional gated implementations; the theme owns rendering. A shared PHP namespace or an accessible class file does not make every class a supported public extension API.

Core owns the shared booking domain and public presentation boundary; Pro owns optional gated implementations; the theme owns rendering. A shared PHP namespace or an accessible class file does not make every class a supported public extension API.

Integrate at the intended boundary

Use exported kimorapro_hb_* functions, documented WordPress hooks, public interfaces and versioned template slots. Core’s facade kimorapro_hb() currently exposes languages() only. Feature presentation is supplied by separate helpers such as kimorapro_hb_has_feature().

Do not instantiate ThemeContract, TemplateResolver, receipt presenters, repositories or private services from a theme. A source reference to those classes explains implementation; it is not a promise that their namespace or constructor is public.

Keep decisions with their owner

Core owns availability, final server quotes, booking snapshots, inventory locking, ledger integrity and shared schema. Pro can supply advanced pricing, coupons/services, online checkout, customer/policy and OTA/iCal implementations through their supported contracts. Pro also has supplemental schema/migrations; do not assume Core creates every Pro-owned table.

The theme must not read license state to decide a premium capability, recalculate a tax, create a payment attempt, reconcile an order on account GET or manufacture a cancellation decision. Use prepared capability/content and authorized owner output.

Identity and lifecycle matter

Free’s canonical folder/text domain is kimorapro-hotel-booking; Pro’s folder is hotel-booking-pro. Commercial product identifiers, template package IDs, retained Pro shortcodes/hooks and request keys have their own contracts. Global prefix replacement is not a migration strategy.

Check public contract versions and register at the documented lifecycle. Early optional-capability queries can be false before compatible add-ons synchronize. Missing Pro should remain a safe Free-only experience, not a class-loading error.

Verify an extension

Test plugin absence, Free-only, optional feature unavailable, supported Pro and current templates separately. Keep source, package, native runtime, browser/provider tests and publication evidence distinct. A version label or metadata declaration does not certify a complete pair.

See public theme contract, gateway extension ownership and schema integrity.

Was this article helpful?

Your feedback helps us improve the documentation.