Quick Search Component not returning Accordion Content | Community
Skip to main content
JonMaguire
JonMaguire
Level 3
August 16, 2023
Solved

Quick Search Component not returning Accordion Content

  • August 16, 2023
  • 1 reply
  • 1194 views

The Quick Search Core Component does not return text results from within the Accordion Core Component. Is this by design, a limitation of the search, or am I missing a configuration somewhere?

I found a similar question from 2017.

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/search-component/m-p/260823

I don't see a resolution in this previous question. Am I to assume I will most likely have to build my own component or somehow extend the Quick Search component to include this content in the search results?

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 Mahedi_Sabuj

By research further on the Query Builder, it has come to light that modifying the oak:index configuration can provide expected results with the Quick Search component.

By default, the full-text search filters operate up to a depth of 3 levels (/oak:index/cqPageLucene/aggregates/cq:PageContent). If your JCR content hierarchy extends beyond this depth relative to jcr:content, you should include additional criteria such as include4, include5, and so forth, in order to encompass those contents within the scope of the full-text search. This approach will enable the search to consider content beyond the initial 3 levels.

The final step involves reindexing the cqPageLucene. This can be done by updating the reindex property to "true".

Reference for AEM Full Text Lucene Search
https://medium.com/@shubhanshu.singh/aem-fulltext-lucene-search-implementation-part-1-cd99687ff736 

1 reply

Mahedi_Sabuj
Community Advisor
Mahedi_SabujCommunity Advisor
Community Advisor
August 16, 2023

Hello @jonmaguire,

You are required to either extend the Quick Search component or build one from scratch. This Quick Search component utilizes Fulltext search to retrieve results. You can find the Java Servlet code for the Quick Search here: Quick Search Java Servlet.

I attempted to use the Query Debugger to perform a search based on the "Accordion content", but unfortunately, I didn't receive any results. I have encountered the same result when attempting searches for 'Tabs' and 'Carousel' content as well.

Mahedi Sabuj
    Mahedi_Sabuj
    Community Advisor
    Mahedi_SabujCommunity AdvisorAccepted solution
    Community Advisor
    August 16, 2023

    By research further on the Query Builder, it has come to light that modifying the oak:index configuration can provide expected results with the Quick Search component.

    By default, the full-text search filters operate up to a depth of 3 levels (/oak:index/cqPageLucene/aggregates/cq:PageContent). If your JCR content hierarchy extends beyond this depth relative to jcr:content, you should include additional criteria such as include4, include5, and so forth, in order to encompass those contents within the scope of the full-text search. This approach will enable the search to consider content beyond the initial 3 levels.

    The final step involves reindexing the cqPageLucene. This can be done by updating the reindex property to "true".

    Reference for AEM Full Text Lucene Search
    https://medium.com/@shubhanshu.singh/aem-fulltext-lucene-search-implementation-part-1-cd99687ff736 

    Mahedi Sabuj
      JonMaguire
      JonMaguireAuthor
      Level 3
      August 18, 2023

      Thank you @mahedi_sabuj! This is exactly the information I needed to move forward.

        Terms & ConditionsAccessibility statement

        Loading footer...