Bloqs fields not being indexed by Low Search
We have a newer site on EE5 running Bloqs 4.0.19 and Low Search 6.2.0 that looks to be running into the same issue as discussed here: https://getsatisfaction.com/low/topic...
The parent Bloq field as well as the atoms themselves are all set to be included in search, and the Page collection in Low Search shows this field and we have the slider set all the way to 3. However, nothing within these fields is appearing in search results. When using the Find and Replace utility within Low Search, it lists all of the other fields available in this channel except for the Bloq field.
Thanks for your help!
Replies
Low 3 May 2019 07:46
The Find &Replace thing is a separate issue; that's purposely limited to certain fields.
As for the Bloqs field not being searchable; were the fields marked as searchable after there was already content in the entries? If so, you might need to re-save the entries to populate the searchable data.
You can try and check the exp_channel_data_field_X table and its field_id_X column (where X is the field ID) for an entry ID and see if there is content in there -- that's the data used for the native Search module, which LS uses to populate its index.
If all of that give you no difference, then I'll need to take a look myself. In that case, send SuperAdmin login credentials to hi at gotolow dot com if you can.
Jarrod Nix 6 May 2019 11:21
I'm fairly certain all fields were marked as searchable prior to adding any content, but I've re-saved several times just to make sure and most of the rows in that table are still empty.
Which reminded me that I forgot to mention we're also using Publisher on this site to allow for multiple languages (which is why we're using Bloqs instead of Fluid fields to begin with). I'm guessing that throws a wrench into things, but I've emailed you login credentials also just in case.
Low 6 May 2019 11:34
I tried to save an existing entry where there was content in the exp_channel_data_field_X table. However, after save, the content in that table for the entry was empty, and therefore the Low Search index for that entry's field, too.
This is a Bloqs issue (possibly with Publisher), so I'd ask BoldMinded about that behaviour.