Child page changes not visible until parent page is published in AEM
In AEM Managed Services, changes made to child pages do not appear on the live site unless the parent page is also published. This behavior affects how navigation, listings, and other parent-driven structures render online. To fix this, identify when the parent page controls child page visibility and publish both the parent and child pages when structural or navigation changes occur.
Description description
Environment
- Product: Adobe Experience Manager (AEM) Managed Services
- Version: 6.5
Issue/Symptoms
- A child page won’t appear on the live site unless its parent page is published.
- Changes such as adding, moving, or reordering child pages aren’t reflected in site navigation or listings until the parent page is published.
Resolution resolution
Publish pages correctly with these steps:
- Check if the parent page includes navigation menus, breadcrumbs, or listings for its child pages.
- If you’ve created new child pages, moved existing ones, or changed their order, publish both the affected child pages and their parent page.
- If you’re only updating content within an existing child page and there are no navigation changes, publish only the updated child page.
- After publishing, confirm that all changes appear correctly on the live site.
Notes:
- Navigation and listings depend on the parent page’s published version. If it doesn’t include updates, changes won’t appear online.
- If publishing fails due to network issues, check replication agent status and logs. AEM doesn’t send automatic failure notifications by default.
- Custom workflow steps can be added to notify administrators of publishing failures if needed.
Related Reading
- Adobe Experience Manager 6.5 documentation home.
- Basic handling in AEM 6.5 LTS User Guide.
- Publishing pages in AEM 6.5 LTS User Guide.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f