How to set sling:resourceType property of AEM page to point page from app/project folder | Community
Skip to main content
M
M1093057
Level 2
October 5, 2022
Solved

How to set sling:resourceType property of AEM page to point page from app/project folder

  • October 5, 2022
  • 1 reply
  • 2376 views

I have customized "/libs/core/wcm/components/page/v3/page/customheaderlibs.html" file by overriding to app/project folder structure (/apps/project folder name/components/page/page/customheaderlibs.html).

 

This is done by modifying sling:resourceSuperType of apps->page folder  to "core/wcm/components/page/v3/page".

 

Now I am facing issue while creating new pages. By default "sling:resourceType" of the new page is pointing to "lib/core/wcm/components/page/v3/page" from libs folder.

 

I wanted this to set value for the every new page sling:resourceType should point to "/apps/project folder/components/page/page" app folder by default. So that it should access my custom code form customheaderlibs.html.

 

Any pointer would be appreciated. Thanks.

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 arunpatidar

you need to replace this in your package and deploy.

you need to change this for template-type as well as templates created with this template-type

1 reply

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
October 5, 2022

you need to set your page type in templates (Structure and initial)

Arun Patidar
    M
    M1093057Author
    Level 2
    October 5, 2022

    @arunpatidar Thanks for your reply.

    Is this under conf folder? Can I modify these values directly for initial & structure. And replace it with "/apps/Project folder/components/page/page"? 

    And while deploying to AEM cloud, do I need to create package & deploy or any other way?

     

     

      arunpatidar
      Community Advisor
      arunpatidarCommunity AdvisorAccepted solution
      Community Advisor
      October 5, 2022

      you need to replace this in your package and deploy.

      you need to change this for template-type as well as templates created with this template-type

      Arun Patidar
        Terms & ConditionsAccessibility statement

        Loading footer...