Aurelia renders the menu selected by WordPress and the multilingual provider. Translating a Page or enabling the language switcher does not automatically translate every custom menu item or assign the correct menu location.
Review each language independently
Open the provider-aware menu administration and inspect the menu assigned to Aurelia’s intended location for each enabled language. Check ordinary Page items, custom URLs, labels, order and published destinations. A missing custom link can reflect the provider’s menu assignment/filtering rather than a theme rendering failure.
For an internal Page, prefer its actual translated Page relationship where appropriate. For custom links, enter a deliberate valid site path or full site URL and verify the resulting rendered href. Do not enter http://rooms/: that identifies a host named rooms, not the site’s Rooms route.
Keep application routes with Core
Rooms, Booking and Search can be managed Pages or supported virtual routes. Their localized destinations must come from Core/provider contracts rather than a theme’s guessed /vi/ prefix or hard-coded slug. Renaming a Page and changing language are separate operations.
Hero and section action URLs have their own Customizer controls; changing a navigation menu does not update those controls automatically. Verify those actions on each language and inspect the canonical destination, including any relevant anchor.
Test the actual journey
Start on a normal translated Page, inspect both menus and switch to its counterpart. Then test Booking/Search routes separately, retaining valid stay inputs and the selected language. Sensitive confirmation/payment/token-bearing requests can intentionally suppress switch links; do not restore them by forwarding their query string through a menu.
Clear the relevant page/menu cache only after correcting the assignment or URL. Do not delete published Pages, rebuild booking routes or globally replace URL prefixes to repair a menu.
