Core provides compatibility adapters for WPML and Polylang and a native WordPress fallback. Themes consume Core’s normalized language contract; they should not call vendor APIs directly or assume another multilingual plugin is installed.
Prepare the provider and content
Install/configure the provider through its own supported workflow and enable the intended languages. Review the site’s default language, translated Page relationships, menu assignments and URL format. Hotel Booking does not configure the vendor’s account or create every translation automatically.
Without a compatible multilingual provider, native WordPress can still supply a single current locale. That does not create multiple language routes or a two-language switcher. When multiple providers are detected, Core’s documented selection favors WPML, then Polylang, then WordPress; avoid running competing site-language configurations unintentionally.
Verify normal routes first
Open a normal published Page in each language and confirm the selected provider supplies valid, credential-free HTTP(S) destinations. Check its translated counterpart rather than expecting every page to map to Home. Configure menus and custom links in each language separately.
Then test the configured Rooms/Booking Pages and supported virtual Search routes. Core handles the application route and language persistence; do not repair a missing translation by hard-coding vendor calls or a language prefix in Aurelia.
Keep translations and permissions separate
Software .mo/JavaScript catalogs translate interface strings. Entity translations cover supported room/amenity and entitled Pro content fields. Neither replaces provider Page/menu configuration or grants a premium capability.
Confirmation/payment/access-token requests can intentionally lock language navigation. A hidden switcher on such a request protects access data and saved booking language; it is not evidence that the provider failed.
Regress the actual provider environment
Use synthetic bookings, a mail sink and approved sandbox integrations. Check normal Page switching, custom menus, CTA submission, virtual routes and saved message/document locale. Source/adaptor tests are not a real WPML/Polylang session or browser certification.
See provider overview and navigation contract.
