Autocomplete/autosuggestions are not language-context sensitive with custom form

Thanks for posting this issue!
However, I don’t think the patch in its current form can be committed, as it assumes that all search pages are filtered by the current content language – which isn’t necessarily the case.

if you are using a custom search form, I’m guessing you also had to implement your own search plugin, correct? Then can’t you just add the appropriate language filter to your implementation of SearchPluginInterface::createQuery()?

@drunken monkey
Actually my scenario is different than the one described in this issue. I've got accents and want search results to show up even if an accent is missing but I want autocomplete to show the correct spelling which has accents. There's other tickets describing this. My setup uses solr.

I see that additional fields are needed for autocomplete with different field types. For now we disabled the jump start accents and stopwords processing ironically to ensure that the correct spelled french language suggestions with accents show up in the suggestions and also to avoid strange stopword issues.

Something else is strange with the acquia cloud environment, possibly edismax is affecting our core. To get a 100% resolution I have to dig in with the search_api_solr_debug module and get a better understanding of what is going on.

For now we were able to make significant improvements by updating our config set to closer to what the jump start has for use with solr 8.11.2