A translated heading, language switcher, menu assignment and booking form destination are separate layers. Identify the failing layer before rewriting URLs, changing stored locale or adding vendor logic to a theme.
Check normal navigation
Inspect the current provider and a normal translated Page first. Verify each language’s menu location, Page relationships and custom link labels/destinations. Missing custom links often need provider-aware menu assignment rather than a new theme fallback menu.
Check actual rendered URLs: http://rooms/ is a host, not an internal path. Hero/section action settings are separate from the header menu. Do not globally prepend a language prefix to external or already localized URLs.
Check application routes
Rooms/Booking managed Pages and virtual Search/booking routes have different owner resolution. Use Core’s current public helpers and Page assignments. Switching a normal Booking surface should retain its safe corresponding surface when available, not silently return to Home.
For a CTA returning to the default language, inspect the native action URL and validated hb_language field, valid stay inputs and the relevant language-specific cache. Reproduce with synthetic dates and one clean request before clearing caches.
Recognize intentional suppression
Single-language, unavailable, provider-error and sensitive locked contexts can hide switch links. Confirmation/payment/nonce/token-bearing requests are intentionally protected. Do not copy their query fields into a fabricated switch URL or alter a saved booking locale to repair presentation.
If the installed helper facade differs from an old guide, verify the actual bootstrap. Current Core exposes kimorapro_hb()->languages(); retained Pro protocols have their own names and must not be renamed by blanket replacement.
Keep source/native tests separate from a real WPML/Polylang/browser session. See route persistence and per-language menus.
