Enable rollout support for existing content fragment folders in AEMaaCS without recreating or deleting folders
In Adobe Experience Manager as a Cloud Service Assets, manually created Content Fragment folders outside the required MSM hierarchy do not support rollout features, which blocks the creation of Language Copies and Live Copies. This article describes how to enable rollout support for existing CFs without deleting or recreating folders and without impacting already published content.
Description description
Environment
- Product: Adobe Experience Manager as a Cloud Service(AEMaaCS) – Assets
- Instance: Development, Stage, Production
Issue/Symptoms
Existing content fragment folders do not have the required MSM (Multi Site Manager) relationship hierarchy due to manual creation. This prevents the creation of Language Copies and Live Copies and blocks rollout functionality. There is concern about the potential impact on published content and downtime if restructuring is attempted.
Resolution resolution
To fix this issue, follow these steps:
- Create a proper blueprint folder structure (for example, under
language-masters) - Use the Assets console to create Live Copies from the blueprint folder to the required locale folders.
- Keep all existing published content fragments in place during the migration.
- Gradually update page or headless references so they point to the MSM managed content fragments in the Live Copy structure.
- After all references are updated and validated, decommission or archive the old manually created folder structure.
- Verify that rollout functionality works as expected with the new structure and confirm there is no impact on published content.
Notes
- MSM relationships for Content Fragments are only created when a Live Copy is made; there is no supported way to retroactively enable MSM on existing manually created folders.
- Do not delete published content fragment folders directly, as deletions replicate to Publish environments.
- Moving or copying content through the Assets console updates references that use standard AEM link mechanisms.
- This approach allows migration with no downtime when it is properly planned and validated in a non-production environment first.