


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!
Views
Replies
Sign in to like this content
Total Likes
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
Please ensure you have the below property on your XFs.
cq:xfVariantType -> web
Thanks!
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
Please ensure you have the below property on your XFs.
cq:xfVariantType -> web
Thanks!