- Issue created by @AaronBauman
- Assigned to AaronBauman
- πΊπΈUnited States AaronBauman Philadelphia
Doing some debugging - looks like porterstemmer is not running during search index, because the langcode is set to 'und' instead of 'en'.
However, when the preprocess method is called during serach, the langcode is set to 'null', so porterstemmer does get invoked.
This breaks the search results.Not sure if this is a Drupal core bug, or porterstemmer bug, but it's definitely a bug.
I'm not using any multilingual / i18n / or anything - it's only English, which i imagine is a pretty common setup.
Opening a MR to add 'und' handling into the processor, but not sure if that's universally appropriate or what.
- @aaronbauman opened merge request.
- Status changed to Needs review
about 1 year ago 2:20pm 6 October 2023 - πΊπΈUnited States AaronBauman Philadelphia
Here's an updated test that demonstrates the current bugginess around search for language-unspecified and non-english language results.
Seems like the existing test is quite insufficient, or at least I don't understand how it's supposed to work.This problem appears to be more pervasive than the current title implies, but i'm not gonna keep changing the title.