A setting does not change the page
Use this guide when a POM Theme setting saves successfully but the visible page does not change.
Confirm the target
On a WordPress multisite network, each site has its own content and settings. Compare the site address in the administration bar with the public URL, then confirm the language and content item being viewed.
Change one setting at a time, save it and record the old and new values. A clear before-and-after test prevents another simultaneous change from masking the result.
Find the effective owner
POM Theme output can be controlled at several levels. Check from the most specific to the broadest:
- The component’s own Page Builder setting.
- Its parent column or row.
- Page-level layout and custom styling.
- The assigned archive, feed or single template.
- The content model or feature configuration.
- Global options under Settings → POM Theme.
A local value can intentionally override a global default. Changing the default will not replace an explicit component or page value.
Verify the setting applies here
Check that:
- The related feature is enabled.
- The current post type, archive, taxonomy or template family supports the setting.
- The page uses the expected header, footer, sidebar or template.
- A permission rule is not serving different output to the current visitor.
- A responsive value is being tested inside its configured viewport range.
Refresh only after configuration is correct
- Save the owning setting.
- Update the affected page or reusable block when it owns page-specific output.
- Purge the affected page cache.
- For stale site-wide styles, run Compile CSS under Settings → POM Theme → Tools → Compile assets.
- Purge any CDN cache and retest while signed out.
Cache clearing cannot make an inapplicable or overridden setting take effect.
Expected result
The page reflects the value from the most specific applicable configuration, and repeating the test in the same context produces the same output.
If the setting still has no effect
Set it back to the original value, then test the nearest specific owner. For example, place an unmistakable temporary value on the component itself. If that works, the global value is being overridden; if it does not, the page probably uses a different component, template or site context.