Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Unfortunately C5 doesn't provide a way to do this -- the only way to tap into the search index is with blocks. And even if you created a phony block just to pass content from the single_page through to the search index, there's no way to say that some content is from one URL while other content is from another URL (which you'd need to do since your single_page controller is handling many different URL's).</p> <p>I don't know of a way to achieve what you want to do (and it appears that nobody else does either -- <a href="http://www.concrete5.org/community/forums/customizing_c5/make-content-in-single-pages-searchable/" rel="nofollow">http://www.concrete5.org/community/forums/customizing_c5/make-content-in-single-pages-searchable/</a> ), other than building your own internal search engine.</p> <p>EDIT: I just did some digging, and thought that perhaps you could manually insert records into the <code>PageSearchIndex</code> table and specify the searchable content and the desired path there -- but this won't work because it relies on one cID (collection id, a.k.a. page id) per entry -- so you'd only be able to insert one record for the top-level single_page path.</p> <p>I think the simplest solution here would be to create your own searching infrastructure for your single_pages (like some kind of function in the controller that would return an array of page paths and searchable content for each one), then override the search block and perform an additional search of your single_page -- then combine the results on the search results page there. Or just use google site search for your site, which will actually crawl the pages and hence find your various single_page urls: <a href="https://www.google.com/cse/" rel="nofollow">https://www.google.com/cse/</a></p> <p>Best of luck.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload