Experience Fragments & OOTB Search | Community
Skip to main content
sachinn20956098
Level 2
September 14, 2021
Solved

Experience Fragments & OOTB Search

  • September 14, 2021
  • 1 reply
  • 1036 views

I'm looking into into leveraging Experience Fragments in AEM 6.4 for a multisite.

 

However, the OOTB search uses a PATH to search for keywords, since the actual /content/site/.. tree will not contain the actual content BUT the references to the Experience Fragments, the search no longer returns results for content. If we include /content/experience-fragment as the search path then it returns the actual XF path itself which is not desired.

 

What would be the recommendation for an OOTB Search implementation? Ideally, the search should just return the content page from where the XF is referenced. Is there any way to achieve this OOTB ? 

 

Thanks in advance! 

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 @sachinn20956098 

 

Experience Fragments support Fulltext Search. So you should be able to use it and it will return the content path where it is referenced, not the XF page path.

I am using it in 2 of the website and it works perfectly fine!

 

Please see the link below:

https://medium.com/@shalima.ebrahim331/adobe-experience-manager-6-5-top-features-c3037bccdae2

 

https://experienceleague.adobe.com/docs/experience-manager-learn/sites/experience-fragments/experience-fragments-feature-video-use.html?lang=en

 

https://github.com/AdobeDocs/experience-manager-learn.en/blob/master/help/foundation/administration/understand-reasons-to-upgrade.md

 

Please ensure you have the below property on your XFs.

cq:xfVariantType -> web

 

Thanks!

1 reply

Asutosh_Jena_
Community Advisor
Asutosh_Jena_Community AdvisorAccepted solution
Community Advisor
September 14, 2021

Hi @sachinn20956098 

 

Experience Fragments support Fulltext Search. So you should be able to use it and it will return the content path where it is referenced, not the XF page path.

I am using it in 2 of the website and it works perfectly fine!

 

Please see the link below:

https://medium.com/@shalima.ebrahim331/adobe-experience-manager-6-5-top-features-c3037bccdae2

 

https://experienceleague.adobe.com/docs/experience-manager-learn/sites/experience-fragments/experience-fragments-feature-video-use.html?lang=en

 

https://github.com/AdobeDocs/experience-manager-learn.en/blob/master/help/foundation/administration/understand-reasons-to-upgrade.md

 

Please ensure you have the below property on your XFs.

cq:xfVariantType -> web

 

Thanks!