I have a problem with some fields in a field collection not being indexed.

The content type "Lösungen" has a field called "Tabs" (field_loesung_tabs), which is a field collection. Within there is a field called "Zweispaltiger Text" (field_zweispaltiger_text), which again is a field collection. And within this collection there a two fields "Linke Spalte" and "Rechte Spalte" (field_linke_spalte and field_rechte_spalte) that are long text fields. I added the follwoing fields and combinations to my fuzzy index:

Tabs
Zweispaltiger Text
Tabs » Zweispaltiger Text
Tabs » Linke Spalte » Text
Tabs » Rechte Spalte » Text
Zweispaltiger Text » Linke Spalte » Text
Zweispaltiger Text » Rechte Spalte » Text
Tabs » Zweispaltiger Text » Linke Spalte » Text
Tabs » Zweispaltiger Text » Rechte Spalte » Text

But none of these seem to work. The content of the fields "Linke Spalte" and "Rechte Spalte" seems not to be in the index and cannot not be found by the search. It does not seem to be a general problem with field collections as other fields from field collections are getting indexed.

Any suggesions what I should change or add to the index?

Comments

ultrabob’s picture

ultrabob CreditAttribution: ultrabob commented
Issue summary: View changes

Funny to be commenting on a 5 year-old issue, but I can confirm this issue, I guess that i because the module is unmaintained.

AstonVictor’s picture

AstonVictor CreditAttribution: AstonVictor at DevBranch commented
Related issues: +#1795712: Index content of Field collection field for search
Mario Steinitz’s picture

Mario Steinitz
Location Hong Kong Central
CreditAttribution: Mario Steinitz at SHORELESS Limited commented
Status: Active » Postponed (maintainer needs more info)

The issue "the module is unmaintained" has been fixed. - I'm currently doing my best to clean up the issue queue and resolve issues as good as I can.

@ultrabob, would you please share some of your (more recent) configuration that is not working as expected? So that I can reproduce the issue and determine, whether it is related to fuzzysearch and how we could get it fixed.

I'll set this issue to "Postponed" until we have enough information to reproduce it. Feel free to add a reproducible setup and set it back to "Active".