Core Search Content Fragments in Pages | Community
Skip to main content
jetate
jetate
Level 4
June 16, 2020
Solved

Core Search Content Fragments in Pages

  • June 16, 2020
  • 2 replies
  • 2090 views

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.

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 vanegi

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.

2 replies

vanegi
Adobe Employee
vanegiAdobe EmployeeAccepted solution
Adobe Employee
June 17, 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
    jetateAuthor
    Level 4
    June 17, 2020

    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.

    jetate
    jetateAuthor
    Level 4
    June 19, 2020
    This is not solved.
    Terms & ConditionsAccessibility statement

    Loading footer...