Bug #19195
closed
Indexed search saves characters in word table with different encoding than in content table
0%
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)
Updated by Eikaa about 16 years ago
i can confirm this behaviour. i also noticed that, if the word contains a dash for instance "blöder-indexer" it's indexed correctly and you can search for "blöder"
Updated by Dmitry Dulepov over 14 years ago
This happens if you add SET NAMES after creating tables. Fields in your tables now use incorrect encoding. You have to convert each field to UTF-8 (not just table but also each field!). Search the bug tracker for the proper way to do it. Or better: drop and recreate the table.
Updated by