Hi @prasanth_s ,
I faced the same issue and after some trial and error I found the correct way to have template-specific page properties in AEM 6.5.
The dialog is not taken from the template node itself — it is taken from the **page component** (sling:resourceType of the template’s jcr:content).
So the proper solution is:
1. Create your own **custom page component** (not a normal component)
Example path:
`/apps/myproject/components/page/custom-standard-page`
2. On this custom page component set
`sling:resourceSuperType = <your-parent-page-component>`
(usually `/apps/myproject/components/page` or the WKND one you are extending)
3. Now override only the dialog (or parts of it) using Sling Resource Merger:
Create
`/apps/myproject/components/page/custom-standard-page/cq:dialog`
and on the `cq:dialog` node add
`sling:resourceSuperType = <parent-page-component>/cq:dialog`
4. Inside this dialog you can now:
- Add your own fields
- Hide unwanted fields (using granite:class or sling:hideResource)
- Re-order tabs/fields with sling:orderBefore
5. Finally, go to your editable template
`/conf/myproject/settings/wcm/templates/page-standard/structure/jcr:content`
and change
`sling:resourceType = /apps/myproject/components/page/custom-standard-page`
That’s it! Now only pages created with this template will show your customized page properties dialog. All other templates keep using the original dialog.
This is the cleanest and recommended way (no copying of entire /libs structure, fully upgrade-safe).
Useful references:
- https://experienceleague.adobe.com/docs/experience-manager-65/developing/extending-aem/extending-pag...
- https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/customiz...
- Sling Resource Merger explanation: https://experienceleague.adobe.com/docs/experience-manager-65/developing/extending-aem/sling-resourc...
It worked perfectly for me. Let me know if you still face any issues!
Thanks,
sai
