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?

CommentFileSizeAuthor
#1 1992602-1--spelleck_field.patch2.06 KBdrunken monkey
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
CreditAttribution: drunken monkey commented
Status: Active » Needs review
FileSize
1992602-1--spelleck_field.patch2.06 KB

This patch would fix spellchecking for the Search API.

pwolanin’s picture

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"

Nick_vh’s picture

Nick_vh
he/him
Location Ghent
CreditAttribution: Nick_vh commented
Status: Needs review » Reviewed & tested by the community

Looks correct - seems an error slipped in somewhere.

pwolanin’s picture

pwolanin CreditAttribution: pwolanin commented
Status: Reviewed & tested by the community » Fixed

committed, thanks

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

kenorb’s picture

kenorb CreditAttribution: kenorb commented

Related: #1954824: Search API Spellcheck doesn't work with Search API Acquia