Hi,
We’re trying to fetch content from fields within a grid field on simple search. Unfortunately, it doesn’t seem to be working.. content from non-grid based fields are being searched fine. We’ve tried searching for content within a grid field that’s “rich text editor” and “text input” without luck. Grid field and sub grid field both are marked “Include in search?”.
Just trying to figure out, if anyone can point us where we’re going wrong or if it’s something on v3.3.0?
Search syntax:
{exp:search:simple_form form_class="search-form" form_id="search-form" result_page="/search/results" no_result_page="/search/no-result" search_in="everywhere" channel="not global_changes|awards" where="any"}
Thanks!
I’m having the same issue on v2.9.0. Grid field is set to searchable, as is the column that I want to search on. I can get results if I search on keywords in the title or a non-grid textarea field, but no results are showing up for keywords exclusive to the grid field.
{exp:search:simple_form channel="clients" search_in="entries" where="any" result_page="search/results" no_result_page="search/no-results" results="20" show_future_entries="yes" status="open"}
I’m guessing I probably overlooked something simple, but I can’t seem to figure it out.
It seems my issue was related to entries that were created prior to setting the field and columns to searchable. New entries in the grid fields show up, but the ones that were entered prior to changing the field and columns to searchable would not. Tried clearing the cache to see if that would resolve the issue, but it did not. I ended up resubmitted those entries (which is a pain if you have a lot of entries) and now they seem to be working.
Hey doubleclick, could your issue be related to this bug?
What happens is if you switch a grid field/row to searchable, existing entries weren’t updating to be searchable. So NEW entries with a searchable grid field are found, but entries made before the field was set to searchable aren’t.
To see if that could be the problem- go find an entry you’re sure should be found but isn’t and just resave it in the cp. If it’s found now? That was the problem.
The bug was fixed in 2.11.0, so either updating and resaving the fields or resaving the entries in question would be the fix- if this is what’s going on.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.