Missing Configuration/Setting to allow new XF Templates in my Project | Community
Skip to main content
T
Thomas-1977
Level 3
September 18, 2018
Solved

Missing Configuration/Setting to allow new XF Templates in my Project

  • September 18, 2018
  • 11 replies
  • 4436 views

I've been rewalking through all the online Template Editor and Experience Fragment (XF) documentation but I must be missing something because I can't seem to make a new XF Template, that is stored under my own project show up properly in the interface for use.

I can take the same template and copy it under the We.Retail project and it shows up just fine after I rename it, but as soon as I move it into my own project it won't show up.  I've tried this with a copy of the We.Retail example XF Fragment Template as well as with one of the base ones from AEM 6.3 under libs.

So my assumption is that there is a configuration setting somewhere for my project which I'm missing that will allow this new XF Template to show up in my project.

Thoughts?

AEM Version - 6.3.2.

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 smacdonald2008

After talking to an internal person - they stated --

I believe it is the cq:allowedTemplates property on /content/experience-fragments node that drives the availability of XF variations:

11 replies

Show previous replies
rupalig70586203
rupalig70586203
Level 2
September 21, 2018

Hi Thomas,

For this you need to create template type based on which you will create template.

Now once you are done with template creation edit you template policies to allow components in your xf page.

Then go to templates console(Tools->general->templates) and enable your template. If its in draft status you will not see your template to create XF.

Once you have enabled template, you can see it to create XF.

Hope this helps you!

Terms & ConditionsAccessibility statement

Loading footer...