New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Entries search filter does not support umlauts (and probably other "exotic" chars) #3145
Comments
Just noticed the php intl extension isn't installed..this can probably be closed. Will do so once search indices are rebuilt and I can confirm. |
This is happening because element search keywords and search query terms both get normalized into ASCII, and the ASCII replacement could vary depending on language. So if the I’m guessing if you change your account’s Language preference to German (Deutsch), then your search query will work as expected. |
Thanks! |
It would be nice if the search query got normalized to the current site’s language. |
@carlcs In general it does. Where are you seeing that to not be the case? |
When searching in the control panel on Element Index pages. In my case I have an entries section with entries which have titles starting with “Tür”. When users are using German for their control panel language, they can find these entries when searching for What I’m proposing is that it shouldn’t matter what language they have configured, and the normalization of the search query should depend on the language the currently selected site on the Element Index page is using. |
@carlcs Whoops, that’s how it was supposed to work but the selected site wasn’t getting carried all the way to where keywords were normalized. Fixed for the next release. |
@carlcs 3.5.17.1 is out now with that fix. |
Description
A lot of German language words (and probably most other languages except English) will not be found in the entry/category filters.
Steps to reproduce
See https://imgur.com/a/5nTKJVk
Additional info
PHP version | 7.1.18
MySQL 5.7.22
Craft Pro 3.0.16.1
The text was updated successfully, but these errors were encountered: