Issue Bug Closed

#19195Indexed search saves characters in word table with different encoding than in content table

Sacha Vorbeck 08/05/08, 17:00 updated 10/02/18, 12:29

Description

I added the line
$TYPO3_CONF_VARS[‘SYS’][‘setDBinit’] = ‘SET NAMES utf8;’;
to the localconf.php and all chars are no written to the DB correctly.

When using the info-module: “INFO->Indexed Search->Words and content”, I can see that in the content-column german umlauts and other special chars are displayed correctly. But in the words column the umlauts are cryptic.
e.g.: aboanträge vs. aboanträge

The same goes for looking at the index_words table with phpmyadmin. In all other tables (tt_content, pages…) the chars are displayed correctly.

So it seems that indexed search uses a different way to create the DB-entries in the word table than it does for the content.

I also noted that the cb_indexedsearch_autocomplete extension doesn`t display the umlauts correctly but I`m not sure if that`s a problem with the extension are also relates to the encoding in the words table.

TYPO3 4.2.1 installation with
indexed_search 2.11.0 and
cb_indexedsearch_autocomplete 0.3.0
(issue imported from #M9125)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.