Skip to main content
Sharvesh106
Level 2
Jul 18, 2024 1:31 PM UTC
Solved

Template Folders not visible on Templates page at /libs/wcm/core/content/sites/templates.html/conf in AEM Cloud Envs(Dev, Stage, QA, & Prod).

I can navigate to the particular templates folder via Url directly, but Templates does not show the folders. It happens only in Cloud envs.

In my local AEM Cloud SDK, it works fine. What could be the possible reason and how to resolve it?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Sharvesh106
Sharvesh106Accepted solution
Level 2
Jul 22, 2024 9:52 AM UTC

Hi, 

The issue was resolved after setting up a new instance and I took a fresh build of the code. 

I believe the repo must be corrupted in Crx for some reason.

8 replies

MukeshYadav_
Community Advisor
Community Advisor
Jul 18, 2024 1:38 PM UTC

Hi,

Template does not show in folders while creating page? you may have to commit all the policies related to template like allowed path and others.

Check if this helps https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/template-not-appearing-while-doing-quot-create-page-quot/m-p/173622

Thanks

Translate
Sharvesh106
Level 2
Jul 18, 2024 1:40 PM UTC

@mukeshyadav_ - In General --> Templates menu, folders are not visible to access and edit the templates. It works fine when we create pages.

Translate
MukeshYadav_
Community Advisor
Community Advisor
Jul 18, 2024 1:43 PM UTC

Hi,

I think re indexing may solve issue https://www.shsteimer.com/blog/posts/aem-editable-template-folders-missing

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/folders-not-visible-on-templates-page-at-libs-wcm-core-content/m-p/280099

 

Also quick check 

Can you check if "editable templates" is selected for the projects under Tools--> General--> Configuration Browser? and below permission are required

 

Thanks

Translate
Sharvesh106
Sharvesh106AuthorAccepted solution
Level 2
Jul 22, 2024 9:52 AM UTC

Hi, 

The issue was resolved after setting up a new instance and I took a fresh build of the code. 

I believe the repo must be corrupted in Crx for some reason.

Translate