Template Folders not visible on Templates page at /libs/wcm/core/content/sites/templates.html/conf in AEM Cloud Envs(Dev, Stage, QA, & Prod). | Community
Skip to main content
Sharvesh106
Level 2
July 18, 2024
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).

  • July 18, 2024
  • 2 replies
  • 1638 views

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.
Best answer by Sharvesh106

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.

2 replies

MukeshYadav_
Community Advisor
Community Advisor
July 18, 2024

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

Sharvesh106
Level 2
July 18, 2024

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

MukeshYadav_
Community Advisor
Community Advisor
July 18, 2024

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

Sharvesh106
Sharvesh106AuthorAccepted solution
Level 2
July 22, 2024

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.