Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I just realized that when fixing the spellchecker (#1859232: Make the naming for the extra included schema types and fields more general as we expect, according to a quick git bisect
) you used content
as the source field for the spellcheck index. This field isn't used by the Search API, we used spell
as the source for the spellchecking.
I don't know whether the change was deliberate, or an oversight, but in any case it breaks spellchecking in the Search API. So can we please switch back to using spell
again, which is available for both modules?
Comment | File | Size | Author |
---|---|---|---|
#1 | 1992602-1--spelleck_field.patch | 2.06 KB | drunken monkey |
Comments
Comment #1
drunken monkeyThis patch would fix spellchecking for the Search API.
Comment #2
pwolanin CreditAttribution: pwolanin commented@drunken monkey - looks like a cascading error where maybe I copied an earlier mistake in our config. It should indeed be "spell"
Comment #3
Nick_vhLooks correct - seems an error slipped in somewhere.
Comment #4
pwolanin CreditAttribution: pwolanin commentedcommitted, thanks
Comment #6
kenorb CreditAttribution: kenorb commentedRelated: #1954824: Search API Spellcheck doesn't work with Search API Acquia