In November 2014 the #2294645: Support aggregate fields patch get committed into search_api_solr_et, but there is no way to specify when an aggregated field (or in general when a fulltext field) should or should not be indexed as "translatable".
Patch attached (will follow a subsequent patch also to search_api_solr_et, following #2294645: Support aggregate fields )
The following patch adds such possibility to FullText aggregated fields (when SearchAPI ET is enabled). The patch is for search_api since it seems impossible to alter the aggregate_field form permanently: using hook_form_alter() a new select form item can be added, but its configuration is lost after saving.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | search_api_et-2502883-7.patch | 2.52 KB | thepanz |
Comments
Comment #1
thepanz commentedComment #2
drunken monkeyNo, definitely not, sorry. I won't add such specific code to the Search API, which is a framework module above all.
However, it seems your problem could easily be solved by overriding the plugin class for the "Aggregated fields" data alteration? Maybe that could just happen in the Search API ET module.
Comment #3
thepanz commentedYes, you're right.
Do you have any pointers to such class overriding technique you suggest to apply?
Thank a lot! :)
Comment #5
thepanz commentedIssue moved to "SearchAPI ET" (was on "SearchAPI").
Patch removed, since it's not correct anymore.
Comment #6
thepanz commentedPatch re-roll.
Implemented using class override.
Comment #7
thepanz commentedMinor notice message fixes.
Comment #8
thepanz commentedPatch rerolled against latest 2.x-dev
Comment #9
thepanz commentedRemoved wrong patch, file from comment #7 works with current 2.x-dev branch.