AEMasCS : Page replication issue (OOTB design reference /libs/settings/wcm/designs/default ) | Community
Skip to main content
Vaibhavi_J
Level 7
July 4, 2026
Solved

AEMasCS : Page replication issue (OOTB design reference /libs/settings/wcm/designs/default )

  • July 4, 2026
  • 2 replies
  • 63 views

Hi Team,

We recently migrated our application to AEM as a Cloud Service. During page replication,  

/libs/settings/wcm/designs/default path included in the publish references.

 AEM as a Cloud Service, /libs is immutable and should not be published. As a result, page publication is blocked unless we manually uncheck this reference in the publication wizard and then proceed with publishing the page. To confirm we do not have any reference to this path in code.

Has anyone encountered this behavior before or knows what could be causing this OOTB reference to be added during publication? Is there any known component, policy, style system configuration, or reference provider that could introduce this dependency?

Any insights or suggestion would be greatly appreciated.

Many thanks in advance!

Best answer by Vaibhavi_J

Able to resolve the issue. This occured due to ACS Commons Design Refrence feature is enabled in application which will add the design refence aong with OOTB /libs design path. We have removed this feature as its not needed on AEMasCS

2 replies

MasonReed11
Level 2
July 6, 2026

This is often caused by a leftover legacy design reference (cq:designPath) or an old static template from the migration. I'd check templates, page properties, and any custom ReferenceProvider implementations. Enabling DEBUG logs for reference collection during publish can also help identify exactly what's adding /libs/settings/wcm/designs/default to the publish references.

Vaibhavi_J
Level 7
July 6, 2026

Thanks for reponse . To confirm we dont have any static template and its refrence .All are editable templates. Also no legacy refrence 

Vaibhavi_J
Vaibhavi_JAuthorAccepted solution
Level 7
July 6, 2026

Able to resolve the issue. This occured due to ACS Commons Design Refrence feature is enabled in application which will add the design refence aong with OOTB /libs design path. We have removed this feature as its not needed on AEMasCS