I created a Sightly PageComponent and Template. I am able to select the Template when creating a new Page and everything seems to work ok. However, when I go to edit the Page Properties in the Touch UI, the Tags control renders differently than the Tags control for a Page that uses a non-Sightly Template/PageComponent and if a Tag is not selected, the Page Properties will not Save. I am running AEM 6 SP2. Is there an additional Hot fix/Feature pack that needs to be installed for this to work properly? I've attached screenshots of the Basic tab of the Page Properties dialog in the Touch UI for both a page based on a Sightly and non-Sightly Template.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi,
Sightly itself does not influence the way how dialogs are displayed. Sightly and JSP act on the same level (from a component perspective) an don't have an impact on the way a dialog is displayed. Are you sure, that you have the very same dialog definition?
kind regards,
Jörg
Views
Replies
Total Likes
Hi,
Sightly itself does not influence the way how dialogs are displayed. Sightly and JSP act on the same level (from a component perspective) an don't have an impact on the way a dialog is displayed. Are you sure, that you have the very same dialog definition?
kind regards,
Jörg
Views
Replies
Total Likes
Hi Jörg,
For this example, I am not using out of the box dialogs and not overriding anything.
Views
Replies
Total Likes
To follow up on the point that Joerg made -- see this community article on Sightly:
https://helpx.adobe.com/experience-manager/using/creating-sightly-component.html
There is no such thing as a Sightly template. A template is separate from Sightly.
A component that you can drag onto a page can be written in Sightly or JSP. The same dialog works for both JSP or Sightly.
Views
Replies
Total Likes
Here is the xml for my template. Please let me know what is incorrect.
<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"
jcr:description="Base page template"
jcr:primaryType="cq:Template"
jcr:title="Base 
 page template
"
allowedPaths="[/content(/.*)?]"
ranking="{Long}1"
shortTitle="Base Content Page">
<jcr:content
jcr:primaryType="cq:PageContent"
sling:resourceType="wcm/foundation/components/page"/>
</jcr:root>
Views
Replies
Total Likes
Can you try to use this as the sling:resourceType "foundation/components/page"?
Views
Replies
Total Likes
I do not have the issue when the sling:resourceType is "foundation/components/page".
Views
Replies
Total Likes
Views
Likes
Replies