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

Avatar

Avatar

nikunjj81682294

Avatar

nikunjj81682294

nikunjj81682294

09-09-2019

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

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

jbrar

Employee

Avatar

jbrar

Employee

jbrar
Employee

09-09-2019

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.

Answers (5)

Answers (5)

Avatar

Avatar

nikunjj81682294

Avatar

nikunjj81682294

nikunjj81682294

09-09-2019

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

Avatar

Avatar

nikunjj81682294

Avatar

nikunjj81682294

nikunjj81682294

09-09-2019

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.

1830278_pastedImage_0.png

1830279_pastedImage_1.png

I am still getting the same issue.

Avatar

Avatar

nikunjj81682294

Avatar

nikunjj81682294

nikunjj81682294

09-09-2019

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

Avatar

Avatar

Vish_dhaliwal

Employee

Avatar

Vish_dhaliwal

Employee

Vish_dhaliwal
Employee

09-09-2019

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

Avatar

Avatar

Vish_dhaliwal

Employee

Avatar

Vish_dhaliwal

Employee

Vish_dhaliwal
Employee

09-09-2019

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