Issue with converting components to XF. | Community
Skip to main content
jezwn
jezwn
Level 5
February 5, 2024
Solved

Issue with converting components to XF.

  • February 5, 2024
  • 3 replies
  • 835 views

Selecting an AEM component and using 'Convert to XF' option, it creates the XF, but the component doesn't get added to the XF, resulting in a blank XF. For eg, I author an RTE component -> Convert to XF, the XF gets created, but no RTE is found inside the XF that got created.

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 Imran Khan

Please check logs if we are having any custom event listener on page publish which may cause this issue. Else, this should an issue with specific service pack. Not having an issue with experience fragment, component, template, permission or policy. Please try to validate same with other service packs.

As verified, this issue is not present as part of vanilla instance aem-service-pkg-6.5.16-NPR-40173-B02.zip service pack.

3 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
February 5, 2024

Hi @jezwn 
Could you please add more information ? like which AEM version are you using, if you are trying on vanilla instance or you have custom code etc.?
Could you please share as much as possible that helps to reproduce the issue?

Arun Patidar
    jezwn
    jezwnAuthor
    Level 5
    February 5, 2024

    @arunpatidar It's AEM 6.5.16, client environment with custom code in place. The interesting thing is that the issue is only observed in DEV environment.

      arunpatidar
      Community Advisor
      arunpatidarCommunity Advisor
      Community Advisor
      February 5, 2024

      Hi @jezwn 
      Thanks for confirmation, I can try and lets see if I can reproduce ?

      Arun Patidar
        Imran Khan
        Community Advisor
        Imran KhanCommunity AdvisorAccepted solution
        Community Advisor
        February 11, 2024

        Please check logs if we are having any custom event listener on page publish which may cause this issue. Else, this should an issue with specific service pack. Not having an issue with experience fragment, component, template, permission or policy. Please try to validate same with other service packs.

        As verified, this issue is not present as part of vanilla instance aem-service-pkg-6.5.16-NPR-40173-B02.zip service pack.

          kautuk_sahni
          Community Manager
          kautuk_sahniCommunity Manager
          Community Manager
          February 16, 2024

          @jezwn Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

          Kautuk Sahni
          Terms & ConditionsAccessibility statement

          Loading footer...