Bug #33025
closed
empty setDBinit breaks charset in BE page tree
Added by Franz Holzinger almost 13 years ago.
Updated almost 13 years ago.
Description
When I set
$TYPO3_CONF_VARS['SYS']['setDBinit'] = '';
in the Install Tool, then the page tree in the BE shows broken texts when an umlaut is part of the text.
When I remove this line, then the Install Tools has
SET NAMES utf8
set with [SYS][setDBinit]. I did not enter this and localconf.php does not contain it. Maybe Firefox 9.0.1 did. So I must be careful before I put the save button in order not to add the 'SET NAMES utf8'.
The characters in the FE are correct.
See the topic "how to set the charset correctly to UTF-8" on the Developer List.
- Status changed from New to Closed
Of course, you must not empty it, as this overwrites the default value. Remove the line from localconf.php
instead.
- Category set to Install Tool
- Assignee set to Steffen Gebert
I do not understand.
Why is the line $TYPO3_CONF_VARS['SYS']['setDBinit'] = ''; inserted by the Install Tool, when this is wrong?
Because you set it to an empty string. You don't unset it with the Install Tool.
You could argue that this is bad - and it is kind of. But just removing the line from localconf.php
wouldn't work (as there could be previous entries), so this is nothing that can just easily be changed.
So this means that the line
"$TYPO3_CONF_VARS['SYS']['setDBinit'] = 'SET NAMES utf8;';"
in localconf.php
is always active even if this line is not in the configuration file.
I am confused why setDBinit is not empty by default. I am confused because the FE shows a different behaviour for UTF-8 encoding than the BE.
Yes, of course, this line is in config_default.php
- where all the default settings come from.
Also available in: Atom
PDF