Querying Elastic search with german umlauts showing encoding errors #4007

New issue

Open

opened 2026-02-20 16:12:30 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 16:12:30 -05:00

Owner

Originally created by @schapsl on GitHub (Sep 24, 2019).

Search terms with german umlauts are shown with broken encondings on the results page.

Issue

When results from elastic search are displayed and the search term contains german umlauts (or non-ascii utf8 characters) the search term is displayed in the input field again and contains an encoding error.

Displaying results for "Köln" will show "KÃ¶ln" as query string in the input field.

Expected Behavior

The search term should be correctly displayed as

Actual Behavior

Possible Fix

In lib/Search/SearchEngine.php SearchEnging::searchAndDisplay(SearchQuery $query)
remove the call to $this->validateQuery($query);.
$this->validateQuery($query); will be called within $this->search($query); anyway and is not needed for $this->displayForm($query);

Steps to Reproduce

Setup Elastic search
Query for "Köln"

Results or no results, in the following page the input field with the search term will show "KÃ¶ln"

Context

Elastic search is not usable in languages with non-ascii characters.

Your Environment

SuiteCRM Version used: 7.11.5
Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Version 77.0.3865.90 (Offizieller Build) (64-Bit)
Environment name and version (e.g. MySQL, PHP 7): PHP 7.2.1, MariaDB 10.1.30-MariaDB, for Win32 (AMD64)
Operating System and version (e.g Ubuntu 16.04): Windows 10.0 build 17763 (Windows 10) i586

Originally created by @schapsl on GitHub (Sep 24, 2019).  Search terms with german umlauts are shown with broken encondings on the results page. #### Issue When results from elastic search are displayed and the search term contains german umlauts (or non-ascii utf8 characters) the search term is displayed in the input field again and contains an encoding error. Displaying results for "Köln" will show "KÃ¶ln" as query string in the input field.    #### Expected Behavior  The search term should be correctly displayed as #### Actual Behavior   #### Possible Fix  In `lib/Search/SearchEngine.php SearchEnging::searchAndDisplay(SearchQuery $query)` remove the call to `$this->validateQuery($query);`. `$this->validateQuery($query);` will be called within `$this->search($query);` anyway and is not needed for `$this->displayForm($query);` #### Steps to Reproduce   1. Setup Elastic search 2. Query for "Köln" Results or no results, in the following page the input field with the search term will show "KÃ¶ln" #### Context   Elastic search is not usable in languages with non-ascii characters. #### Your Environment  * SuiteCRM Version used: 7.11.5 * Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Version 77.0.3865.90 (Offizieller Build) (64-Bit) * Environment name and version (e.g. MySQL, PHP 7): PHP 7.2.1, MariaDB 10.1.30-MariaDB, for Win32 (AMD64) * Operating System and version (e.g Ubuntu 16.04): Windows 10.0 build 17763 (Windows 10) i586

deekerman added the

Type: Bug

Status:Fix Proposed

Area: Elasticsearch

labels

2026-02-20 16:12:30 -05:00

deekerman commented

2026-02-20 16:12:32 -05:00

Author

Owner

@SuiteBot commented on GitHub (Jan 25, 2022):

This issue has been mentioned on SuiteCRM. There might be relevant details there:

https://community.suitecrm.com/t/alguien-con-elasticsearch-funcionando-correctamente-con-tildes-y-enes/83769/1

@SuiteBot commented on GitHub (Jan 25, 2022): This issue has been mentioned on **SuiteCRM**. There might be relevant details there: https://community.suitecrm.com/t/alguien-con-elasticsearch-funcionando-correctamente-con-tildes-y-enes/83769/1

deekerman commented

2026-02-20 16:12:32 -05:00

Author

Owner

@SuiteBot commented on GitHub (Jan 25, 2022):

This issue has been mentioned on SuiteCRM. There might be relevant details there:

https://community.suitecrm.com/t/somebody-happy-with-suitecrm-7-12-2-and-elasticsearch/83751/3

@SuiteBot commented on GitHub (Jan 25, 2022): This issue has been mentioned on **SuiteCRM**. There might be relevant details there: https://community.suitecrm.com/t/somebody-happy-with-suitecrm-7-12-2-and-elasticsearch/83751/3