Expand my Community achievements bar.

SOLVED

Static Template on the ADOBE AEM 6.4

Avatar

Level 3

Hi Guys,

Anyone had the problem using the component parsys in the Static Template?

I was creating static template but it isn't showing the edit option on the parsys component.

Show the screens bellow.

2019-01-23_11-11-45.jpg

1674561_pastedImage_1.png

1674562_pastedImage_2.png

Anyone can I help me?

Alisson

1 Accepted Solution

Avatar

Correct answer by
Level 10

If you are using static template in touch UI, then you'd need to follow the old approach of adding the components/component group via 'template design'.

  1. Click on the dropdown/caret next to EDIT button, choose 'Design'
  2. Navigate to your parsys component
  3. Add the specific components/groups to that parsys component
  4. Change the mode back to EDIT
  5. Click on the parsys component and you should see '+' sign to add the component(s) to the parsys

HTH

View solution in original post

19 Replies

Avatar

Level 10

I will look into this.

However - in AEM 6.4 - static templates no longer represent best practice. Adobe recommends Editable Templates -- Scott's Digital Community: Guided Journey for Experience Manager on Editable Templates

Avatar

Level 3

smacdonald2008 thank you.

I'll be waiting for your answer.

Avatar

Correct answer by
Level 10

If you are using static template in touch UI, then you'd need to follow the old approach of adding the components/component group via 'template design'.

  1. Click on the dropdown/caret next to EDIT button, choose 'Design'
  2. Navigate to your parsys component
  3. Add the specific components/groups to that parsys component
  4. Change the mode back to EDIT
  5. Click on the parsys component and you should see '+' sign to add the component(s) to the parsys

HTH

Avatar

Level 10

On 6.4 - i setup a little project where my parsys component was embedded into the script of the page - like this:

ParSys11.png

It works fine.

Avatar

Level 3

gauravb10066713 Do we need to do this always when I create the new page?

Avatar

Level 10

that is standard practice. Did it work for you?

Avatar

Level 3

ok smacdonald2008​ but it isn’t working when I do in the main.html of the template.

Avatar

Level 10

Hi,

It works for me as well.

What you need to do is simply test and include the parsys in the component JSP in the below way.

<html>

<%@include file="/libs/foundation/global.jsp" %>

<cq:include script="/libs/wcm/core/components/init/init.jsp"/>

<body>

<h1>Here is where your custom AEM Column component will go</h1>

<cq:include path="par" resourceType="foundation/components/parsys" />

</body>

</html>

It will work. It works for me. Below is the screenshots.

1674713_pastedImage_1.png

1674714_pastedImage_2.png

Hope this helps!!

Thanks,

Ratna Kumar.

Avatar

Level 10

Hi,

If you use HTL i.e, ex: main.html then it is not recommended to use static templates.

Please use Editable templates.

Thanks,

Ratna Kumar.

Avatar

Level 10

you don't need to do it again for any number of pages that you create from that template.

Avatar

Level 3

Awesome!

I’ll try do that and give you the Feedback.

thanks!

Avatar

Level 10

Glad you got it working - this is the benefit of the AEM community!

Avatar

Level 3

smacdonald2008​ I have AEM 6.4.6. While i understand that editable templates are the best option in 6.4.6, does it mean that "normal" are not supported any more? i come from a 6.3 background. I created a few templates under /apps/<project>/templates. I also created a few configurable templates. When i go to sites and do a "new page" i dont see the templates i created under the /apps/<project>/templates but only see the ones which i created as configurable templates. Any idea whats going on here?

Avatar

Community Advisor

Nothing to do with editable/static templates its issue with the allowedtemplate property on your content node likebelow-

You need add your apps folder path like below-

1862658_pastedImage_0.png

Avatar

Level 3

I realized that yesterday. Stupid me.

Avatar

Level 1

Just want to check if we can use touch UI component (sightly) component in static template page?