Missing Configuration/Setting to allow new XF Templates in my Project | Community
Skip to main content
New Participant
September 18, 2018
Solved

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

  • September 18, 2018
  • 11 replies
  • 4435 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

smacdonald2008
New Participant
September 18, 2018

You are having an issue at placing an Experience Fragment in a page that is based on an editable template