Issues while using Experience Fragments in AEM 6.5 | Community
Skip to main content
A
akshayb35452619
Level 2
July 22, 2020

Issues while using Experience Fragments in AEM 6.5

  • July 22, 2020
  • 2 replies
  • 8289 views

Hi All,

 

I am using AEM 6.5 instance. I have created custom editable template and experience fragment based on that custom template. I have created test page based on the same editable template and added Experience fragment component. But while adding or configuring that component, I am unable to add or use my created custom Experience fragment. It is not visible when I browsed it through path browser from Experience fragment dialog.

Any pointers will be helpful.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Vaibhavi_J
Vaibhavi_J
Level 7
July 22, 2020

Hi @akshayb35452619 , 

 

Have you enabled the custom XF in template policy ? 

Policy is like a design mode, where you can control the components to be available on page. 

Please do include custom XF in template policy and it will be available to use on a page. 

 

    A
    akshayb35452619Author
    Level 2
    July 22, 2020
    Hi Vaibhavi, I have added the XF to allowed components for the layout container policy. Still it is not visible to me as mentioned by you in the above screenshot. What might be the issue?
      Vijayalakshmi_S
      Vijayalakshmi_S
      Level 10
      July 22, 2020

      HI @akshayb35452619,

      If you are unable to locate the newly created XF in path browser of XF component (below screenshot 1), then add cq:xfVariantType property to the XF editable template's initial/jcr:content (screenshot 2)

      Example : /conf/learnings/settings/wcm/templates/xf-editable-template/initial/jcr:content

      After setting this, create new XF page out of the XF template and then try locating the newly created XF -> you should be able to see it available as you navigate via Path Browser (Experience fragment variation path) field

      Screenshot 1:

      Screenshot 2:

       

      Reason for adding this :

      If you observe the dialog field (Path browser for choosing XF page), it has a property named "variant" -> web.

      This is compared with cq:xfVariantType property in the XF page (master variation) which will be available if we add it at template level (to be available in all XF pages created out of that template)

      Note : If you don't have any other variation like facebook/pinterest, then we can set it at editable template-type itself. (to flow to template and hence to XF pages) 

        A
        akshayb35452619Author
        Level 2
        July 23, 2020
        Hi Vijaylaxmi, I have added the required property at the node but still issue persists. I am using custom editable template and created XF based on that template. Also testing addition of XF to page created based on that custom Editable template.
          Vijayalakshmi_S
          Vijayalakshmi_S
          Level 10
          July 23, 2020

          Hi @akshayb35452619,

          After adding the property to the editable template, did you try creating new XF page out of it ?

          It might not work for the already created XFs(by then the property is not available)

          Can you confirm on the below

          • By the term " I am using custom editable template and created XF based on that template", you refer to the project specific structure page component created by inheriting from "cq/experience-fragments/components/xfpage" and using that newly created structure component to create editable template-type and hence editable template (initial/jcr:content and structure/jcr:content should point to your newly created structure page component)
          • Experience fragment component that you are using to locate the XF. Is it from "General" component group(/libs/cq/experience-fragments/editor/components/experiencefragment) or proxy component inherited from core component. (/apps/core/wcm/components/experiencefragment/v1/experiencefragment)
            Terms & ConditionsAccessibility statement

            Loading footer...