Unable to add Extended Component to Experience Fragment. | Community
Skip to main content
H
himanshushishodia
August 18, 2021
Question

Unable to add Extended Component to Experience Fragment.

  • August 18, 2021
  • 2 replies
  • 992 views

Hi, 

I have created a extended component in Angular that inherits from the text component referring this article. https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/spa-editor/angular/extend-component.html?lang=en

But the issue is I am able to add this component in AEM Pages but not in Experience Fragement. Experience Fragments is showing it only as the text component, the html that I have added from angular is not showing up. 

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

2 replies

Asutosh_Jena_
Community Advisor
Asutosh_Jena_Community Advisor
Community Advisor
August 20, 2021

Hi @himanshushishodia 

 

It should work on XF as well as it's working perfectly fine on the AEM Page. Do you see any error in the log while rendering the content on XF?

Also I believe there is only one instance of component and correct instance is referred in the XF?

 

Thanks!

    H
    himanshushishodiaAuthor
    August 20, 2021

    Hi @asutosh_jena_ 

    I am new to AEM hence does not know that there are logging for all the actions, Now I have skimmed through the logs and found this error in the logs

     

    21.08.2021 00:41:12.522 *ERROR* [0:0:0:0:0:0:0:1 [1629486672471] GET /content/experience-fragments/wknd-spa-angular/us/en/site/footer/master.html HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=wknd-spa-angular/components/custom-component, superType=null, path=/content/experience-fragments/wknd-spa-angular/us/en/site/footer/master/jcr:content/root/custom_component_1130043739

     

    The issue is that it is a custom component hence there is no superResourceType, but even if I set the superResourceType to some value (that is make this an extended component) the problem is that then it will render only the superResource and not my angular html. This happens only for an XF and not for the page. 

     

    Thanks, 

    let me know if you need any additional information on this. 

      Kishore_Kumar_
      Kishore_Kumar_
      Level 9
      August 28, 2021

      Hi @himanshushishodia ,

       

      Could you please see the recent answers in the below thread and check if it helps ?

      https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-with-spa-editor-how-to-use-the-experience-fragments/m-p/322742 

        H
        himanshushishodiaAuthor
        August 30, 2021

        Hi @kishore_kumar_ 

        I have gone through the post you shared before posting this question. This does not solved my problem also this post is about using an Experience Fragment in the SPA. While I am facing problem while adding an extended component designed using angular in Experience Fragment. 

         

        Thanks!!

        Himanshu

          Terms & ConditionsAccessibility statement

          Loading footer...