Avoid Inherited Widgets and Menus on Custom Pages
This article explains how community tagging affects custom pages and how to avoid unintended navigation or layout changes.
Summary
- Tagging a custom page to a community causes that page to inherit that community’s widgets and menus. To avoid unexpected navigation changes, keep custom pages untagged unless you intentionally want them to adopt another community’s structure and elements.
How tagging affects custom pages
- When a custom page is tagged to a community, the page will inherit that community’s widgets and menus (for example, hero menus).
- Inherited widgets and menus can change the page’s layout or navigation in ways that may be unexpected.
Best practice
- Only tag a custom page to another community when you have a specific, intentional use case that requires the page to adopt that community’s structure and elements.
- For general or standalone custom pages, leave them untagged to avoid unintended layout or navigation behavior.
How to remove inherited menus/widgets (practical guidance)
- If a page is showing inherited menus or widgets after being tagged:
- Remove the community tag from the custom page.
- Resave the page to ensure tags are cleared and the inherited menus/widgets are removed.
If you need assistance
- Support can verify tags and help remove them if needed. Provide the page details when requesting help so tags can be reviewed and the page resaved.
Conclusion
- Tagging enables a custom page to adopt another community’s widgets and navigation, which is useful when intentional. To prevent unexpected layout or navigation changes, keep custom pages untagged unless you want them to inherit another community’s structure; removing the tag and resaving the page will clear inherited menus and widgets.