Page Activation failing when ExperienceFragment is used on the page - 6.5 | Community
Skip to main content
nikunjj81682294
nikunjj81682294
Level 2
Sep 9, 2019 7:11 PM UTC
Solved

Page Activation failing when ExperienceFragment is used on the page - 6.5

Internal Server Error

Exception:

I am getting the above null pointer exception when I try to activate a page using experience fragments on it.

Any help is much appreciated.

Thanks,

Nikunj Jariwala

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
user05162Accepted solution
Employee
Sep 9, 2019 7:50 PM UTC

Checking the AEM code at "com.adobe.cq.xf.impl.ExperienceFragmentsReferenceProvider"

Page parentXf = getVariationParent(path, resolver);

references.add(new Reference(TYPE_XF, parentXf.getTitle(), parentXf.adaptTo(Resource.class), parentXf.getLastModified().getTimeInMillis()));

It looks like the issue is with one of the properties(title,lastmodified) not set on the fragment/variation.

View reply

7 replies

nikunjj81682294
nikunjj81682294Author
Level 2
Sep 9, 2019 9:43 PM UTC

Deleting the XF and readding it resolved the issue. It was the missing cq:lastModified date.

Translate
    raju-komari
    Level 3
    Nov 21, 2022 8:33 PM UTC

    One More underline point is that If cq:lastReplicationAction is present, then cq:lastReplicated (date value) is must in 6.5 of any JCR node property of that page while publishing from author to live 

    Translate
    nikunjj81682294
    nikunjj81682294Author
    Level 2
    Sep 9, 2019 8:15 PM UTC

    JaideepBrar​,

    I see both the properties cq:lastModified and jcr:title are present on both the master jcr:content and the parent of master jcr:content.

    I am still getting the same issue.

    Translate
    user05162Accepted solution
    Employee
    Sep 9, 2019 7:50 PM UTC

    Checking the AEM code at "com.adobe.cq.xf.impl.ExperienceFragmentsReferenceProvider"

    Page parentXf = getVariationParent(path, resolver);

    references.add(new Reference(TYPE_XF, parentXf.getTitle(), parentXf.adaptTo(Resource.class), parentXf.getLastModified().getTimeInMillis()));

    It looks like the issue is with one of the properties(title,lastmodified) not set on the fragment/variation.

    Translate
      nikunjj81682294
      nikunjj81682294Author
      Level 2
      Sep 9, 2019 7:50 PM UTC

      Yes. I m using the master variation. It's a new XF getting deployed from the git repo.

      Translate
      vish.dhaliwal
      Employee
      Sep 9, 2019 7:48 PM UTC

      Question: Are you using the master variation? Have you copied the variation from other XF?

      Translate
      vish.dhaliwal
      Employee
      Sep 9, 2019 7:43 PM UTC

      Hello,

      Firstly, check the references of this page from the References tab in the left hand side. Check if everything looks okay there.

      Secondly, enable a debug log on "com.adobe.cq.xf.impl.ExperienceFragmentsReferenceProvider" and replicate the page again. You should see messages like "Determining references to experience fragments for resource at", "Adding the parent experience fragments as references" etc.

      Hopefully, these messages provide more info to understand the cause.

      Regards,

      Vishu

      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...