Black Friday
Skip to documentation content

Troubleshooting

Diagnose theme layout, cache and asset delivery

Start by identifying the actual parent/child theme and installed bytes. A visual issue can come from stale delivery, unsupported overrides, content configuration, a runtime gate or Core/Pro markup; changing CSS before locating the owner can hide the cause.

Start by identifying the actual parent/child theme and installed bytes. A visual issue can come from stale delivery, unsupported overrides, content configuration, a runtime gate or Core/Pro markup; changing CSS before locating the owner can hide the cause.

Capture the failing surface

Record package versions/commits, route pattern, viewport, browser, locale, logged-in state and first observed symptom. Remove guest/access data from screenshots. Compare Homepage, normal Page and the affected booking/account surface separately.

Inspect delivered CSS/JavaScript filenames and cache versions against the parent manifest and current package. A source file edited locally does not prove its compiled asset was rebuilt or installed. Avoid editing a compiled file alone.

Check contracts and configuration

Review allowed template identities/versions and rejected-override diagnostics through public helpers. Child overrides should fall through safely when incompatible. Do not copy private partials or use CSS to hide a duplicate policy/receipt caused by a broken ownership handoff.

Check the relevant Customizer media, action URLs and Page/template assignment. Room media, global headers and gallery viewer frames have different composition rules. Inspect phone/tablet/desktop and long translated copy rather than assuming a single crop/fixed width suits all views.

Current Aurelia uses its independent shared runtime license gate; a locked presentation needs owner/license diagnosis, not a Pro purchase or CSS workaround. General theme minimums and optional sample-hotel import requirements are also separate.

Recover narrowly

Fix the owning build/configuration/override, then clear the relevant safe cache and check worker/OPcache handling for the actual environment. Preserve Core form hooks, validation fields and payment/status semantics. Do not alter booking data to repair a layout.

Retest the exact original surface and a native fallback with synthetic data. Static asset/hash checks are not cross-browser, keyboard, accessibility or provider E2E evidence. See Aurelia performance/media and safe conflict testing.

Was this article helpful?

Your feedback helps us improve the documentation.