Empty/Blank Page issues with Experience Fragment | Community
Skip to main content
V
v1101
Level 5
May 15, 2021
Solved

Empty/Blank Page issues with Experience Fragment

  • May 15, 2021
  • 2 replies
  • 3083 views

Hello - I am facing some issues with experience fragment(XF). All of a sudden, the experience fragment master variant is empty/blank and I still see the content in the child variations. This is happening for multiple XFs. Not sure what is causing the issue. Could someone throw some light on this?

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 Asutosh_Jena_

Hi @v1101 

 

Can you please check the error log and see what error it is throwing when you are trying to access the master variant?

You can find the error log in aem installation folder crx-quickstart/logs/error.log

 

Also please check if any specific component is present on those pages which all are breaking or it any for all the component.

 

Was there any recent changes that was done to the code are deployed on the instance?

2 replies

Asutosh_Jena_
Community Advisor
Asutosh_Jena_Community AdvisorAccepted solution
Community Advisor
May 15, 2021

Hi @v1101 

 

Can you please check the error log and see what error it is throwing when you are trying to access the master variant?

You can find the error log in aem installation folder crx-quickstart/logs/error.log

 

Also please check if any specific component is present on those pages which all are breaking or it any for all the component.

 

Was there any recent changes that was done to the code are deployed on the instance?

    V
    v1101Author
    Level 5
    May 15, 2021
    @asutosh_jena_ - Thanks for your reply. I don't see any errors in the error log. Moreover, the same set of components is used in the child variation as well. There are no recent changes deployed on the instance.
    Bhuwan_B
    Community Advisor
    Bhuwan_BCommunity Advisor
    Community Advisor
    May 15, 2021

    @v1101 Can you check if you are using OOTB template or your own. Also please check if template's sling:resourceType points to the correct page component. Ensure you have proper user permissions to perform this task.

      V
      v1101Author
      Level 5
      May 15, 2021
      @bhuwan_b - I see this issue started happening recently. Also the template is pointing to correct component. this is happening to some of the XFs only.
      Terms & ConditionsAccessibility statement

      Loading footer...