Skip to documentation content

Troubleshooting

Troubleshoot theme layout, cache and assets

Diagnose Aurelia visual regressions by separating template, responsive image, CSS, cache and child-theme causes with safe checks.

Record the route, locale, viewport and expected component before changing CSS. Check Home, Rooms, Room Detail, Search, Book Now and Confirmation separately; route-specific styles and responsive image slots can make one surface healthy while another is stale. Confirm intrinsic image dimensions, srcset, focal point and reserved ratios before diagnosing a crop as a template defect. Keep external runtime asset dependencies at zero and verify that below-the-fold media is lazy-loaded rather than blocked by an optimizer.

Purge only the relevant page/CDN and object-cache entries, then reload PHP workers when a bind-mounted update may be hidden by OPcache. Compare a cold private window with a warm session and inspect the loaded stylesheet handle. A child stylesheet should load after aurelia-style; an invalid Hotel Booking override must fall through child, parent and plugin default. Do not edit the parent runtime or generated manifest to make a single screenshot pass.

Check keyboard focus, 200%/400% reflow, reduced motion and no-JavaScript navigation while fixing visual behavior. If the symptom occurs only with Pro, verify the optional capability and ensure the Free-only surface still renders. Capture a redacted screenshot with browser, version, viewport and asset URL origin only. Escalate a reproducible regression after caches are cold.

Was this article helpful?

Your feedback helps us improve the documentation.