Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

\/etc/designs folder not installing on publisher

Avatar

Level 2

Hi, we are trying to migrate from 6.5 to AEMaaCS, we have few images left over in /etc/designs so we are trying to leave them as is, but the nodes under /etc/designs are not getting installed in publisher with the pipeline even though the filters are in place(they are installing in author instance but not on publisher). any help would be highly appreciated. 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Based on my recent migration experience, you may need to migrate from the current platform to the cloud using a package approach. For ongoing changes, considering there is no design manager available now in the cloud, you should use a method like the tree activation workflow(or package replication) to activate the changes from Author to publishers.

Regards,
Albin

https://myprofile.albinsblog.com

View solution in original post

5 Replies

Avatar

Community Advisor

In AEMaaCS the usage of '/etc/designs' for storing design configurations has shifted. 
The design and client-side resources are now typically handled through the "/apps" and "/content" paths

In AEMaaCS, "/etc/designs" is deprecated.

Is there any particular reason why you are still housing images under /etc/designs?

Avatar

Level 2

Hi @Rohan_Garg , we are migrating old legacy project to AEMaaCS, we have already migrated clientlibs and designs from /etc but there are few images and other files still leftover, we are considering to move them as part of enhancement since there is heavy code dependency over the files residing under /etc/designs, so can you please help us what should we do for it to get installed on publisher?

Avatar

Community Advisor

Try installing through the package manager: install the package on the Author instance and replicate it to the Publishers. For additional details, refer to Key Learnings from Migration to AEM as a Cloud | by Albin Issac | Tech Learnings | May, 2024 | Mediu...

Regards

Albin

https://myprofile.albinsblog.com

 

Avatar

Level 2

This will work, but the deployment should be with aem cloud pipeline, so we are trying to figure out the issue.

Avatar

Correct answer by
Community Advisor

Based on my recent migration experience, you may need to migrate from the current platform to the cloud using a package approach. For ongoing changes, considering there is no design manager available now in the cloud, you should use a method like the tree activation workflow(or package replication) to activate the changes from Author to publishers.

Regards,
Albin

https://myprofile.albinsblog.com