Core Search Content Fragments in Pages

Avatar

Avatar
Affirm 5
Level 3
jetate
Level 3

Likes

12 likes

Total Posts

69 posts

Correct reply

5 solutions
Top badges earned
Affirm 5
Validate 10
Validate 1
Ignite 3
Ignite 1
View profile

Avatar
Affirm 5
Level 3
jetate
Level 3

Likes

12 likes

Total Posts

69 posts

Correct reply

5 solutions
Top badges earned
Affirm 5
Validate 10
Validate 1
Ignite 3
Ignite 1
View profile
jetate
Level 3

16-06-2020

I am working on rebuilding a site that was originally set up in 6.3. I've run into an issue with the Search feature where it's only searching the metadata for the page and not including the Content Fragments in the search. I've overlaid the Search and Content Fragment components from the Core Components bundle.

 

On our 6.3 instance, search is returning pages based on Content Fragment content but it is not on our 6.5 instance. The original site was built roughly 3 years ago, and I don't know if any configs were changed to enable search of CFs in pages for the results. 

 

I don't believe any modifications were made to the Oak Index. From what I've compared, things look the same on both instances. 

 

If there's an easy way to enable the core Search component to include searching the page Content Fragments, it would be hugely helpful.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile
vanegi
Employee

16-06-2020

Have you enabled debug logs for all the below apis , if not yet can you please do that. DEBUG logging configuration can be added for the following packages, write a separate log file. 

 

org.apache.jackrabbit.oak.plugins.index

org.apache.jackrabbit.oak.query

com.day.cq.search

 

After this, you can run a search both in working [6.3] and non-working [6.5] instance. This way, we can find out if anything is changed, and which particular index is being utilized in both the cases and the query triggering in the backend as well.

jetate

Thanks. I set up the logs, but they are huge. I'm not sure what I'm looking for, but I'm not seeing any red flags. Nothing in search related to content fragments.

I came across this yesterday for OSGi configs for Content Fragments -- https://docs.adobe.com/content/help/en/experience-manager-65/developing/extending-aem/content-fragments-config-components-rendering.html#osgi-service-content-fragment-component-configuration -- after finding older information for a deprecated setting that was not set up on my new instance but was on my old instance. I added my components to the configs but I'm not seeing any changes in the search results.

vanegi
Is the query triggering in the backend in query.log is same for both AEM 6.3, AEM 6.5? Which index is picking here?
jetate

They appear to be the same. I see references to /oak:index/cqPageLucene, /oak:index/lucene, and /oak:index/damAssetLucene.

 

I noticed that the OOTB Content Fragment component under General adds a text node to the content fragment node under the page. This node does not exist when using the Core Content Fragment component. If I add this node to the content fragment node under a page, the contents of that node will show in my search results. 

Answers (0)