Black Friday
Skip to documentation content

Aurelia Theme

Configure Aurelia menus, language switching and Pages

Aurelia owns the header/menu/switcher presentation while Core supplies normalized language navigation and booking routes. WPML/Polylang configuration should not be hard-coded into the theme.

Aurelia owns the header/menu/switcher presentation while Core supplies normalized language navigation and booking routes. WPML/Polylang configuration should not be hard-coded into the theme.

Assign the right navigation

Configure WordPress/provider menus for each enabled language and the intended theme location. Verify Page items and custom links, labels and order independently. Translating a Page or enabling the theme switcher does not automatically assign all custom menu items.

Check hero and section actions separately from the main menu. Use actual site paths or full URLs, and inspect rendered destinations on both languages. A root-relative path is different from a host such as http://rooms/.

Read switcher availability

The theme consumes kimorapro_hb()->languages() after probing the navigation contract. It renders only a valid ready snapshot with enough usable language items and one current language. Single-language, unavailable, malformed, provider-error and locked states can hide the switcher safely.

Sensitive booking/payment/confirmation/nonce/token requests intentionally suppress switch links. Do not forward their query parameters to manufacture another-language URL. For normal Pages and virtual Booking/Search surfaces, test the corresponding destination rather than accepting an unexpected return to Home.

Secondary Pages and shared shell

Review the intended Page template/content, publication status and context-specific header media. Theme navigation must use Core’s assigned Page/route helpers where applicable; a familiar slug is not proof of route ownership.

Contact uses Free’s configured form/readiness; account surfaces require their owning Pro capability. A Page existing in WordPress does not prove its application workflow is enabled. Avoid changing a private Page to public merely to repair a navigation symptom.

Verify safely

Test normal Page switches, custom links, CTA submission and native virtual routes in each language, including long labels/mobile navigation. Use synthetic booking data and inspect current provider/cache state before editing routes.

See per-language menu setup and route persistence.

Was this article helpful?

Your feedback helps us improve the documentation.