POM Theme help
Use this chapter when a saved POM Theme configuration does not produce the result you expected. Each guide starts with the visible symptom and follows the shortest safe route to the setting, content or context that owns it.
Start with the symptom
- Builder content is missing — find whether the content is absent, hidden, restricted or owned by a reusable block.
- A responsive layout looks wrong — isolate breakpoint, visibility, width, spacing and source-order problems.
- A setting does not change the page — identify the effective scope and any more specific override.
- Generated CSS appears stale — distinguish an unsaved configuration from old generated assets or cached output.
- A dynamic template is not being used — verify the template family, assignment and current request.
- A merge tag returns an empty value — check tag family, field key and preview object.
- Facets return unexpected results — compare the query source, mapped data and active URL state.
- A form does not submit — locate validation, conditional, upload, consent, spam or action failures.
- Information to collect before contacting support — prepare a useful report without exposing secrets or personal data.
A safe first pass
Before changing several settings at once:
- Open the affected public URL in a private browser window.
- Record the exact expected and actual result.
- Confirm that you are editing the same site, language and content item shown by that URL.
- Change one relevant setting, save it and repeat the same test.
- Clear page or CDN caches only after confirming the saved configuration.
This order preserves the evidence needed to identify the owner of the output. Generated files and cached HTML can make an old result persist, but they cannot correct a wrong template assignment, query source or field mapping.
Before asking for help
Do not send passwords, license keys, API credentials, cookies, nonces, database exports or unredacted customer data. Use the support-information guide to produce a minimal reproducible report.