Pages published when a content fragment is published in AEM
When publishing a content fragment in ÃÛ¶¹ÊÓƵ Experience Manager (AEM), pages referenced by the content fragment may be published automatically. This article provides steps to manage this process and ensure only desired items are published.
Description description
Environment
- Product: ÃÛ¶¹ÊÓƵ Experience Manager (AEM) Managed Services; ÃÛ¶¹ÊÓƵ Experience Manager as a Cloud Service (AMaaCS)
- Version: AEM v6.5; any AEMaaCS release
- Environment Type: Production
- Product Offering: Sites
Issue/Symptoms
- Publishing a content fragment causes all its references, including pages, to be published automatically.
- The quick publish option does not notify that referenced pages will be published.
- The Manage Publication  wizard provides details of references but requires additional steps to access this information.
- The pop-up notification for publishing does not list page paths or allow deselection of referenced items.
Resolution resolution
This behavior is by design and ensures consistency between the author and publish environments. When a content fragment is published, all its references—including other content fragments, assets, and pages—are published to maintain synchronization.
To better manage this process and view detailed reference information before publishing:
- Navigate to the Manage Publication  wizard in AEM. In Step 2 of the wizard, click the Published References button. This displays a detailed list of all references (e.g., pages, assets) included in the publication process.
- Within the Published References  section of the Manage Publication wizard, you can manually deselect any items you do not wish to publish.
Note that when using quick publish, all references are automatically included without explicit notification or options for exclusion. This is intended for streamlined workflows where detailed review is not required. By following these steps and utilizing the Manage Publication wizard for more granular control over publication processes, you can ensure that only desired items are published while maintaining synchronization across environments.