[TYPO3-dev] Weird Upgrade Problem 4.1.x -> 4.2.x
Steffen Kamper
info at sk-typo3.de
Thu Mar 19 11:29:53 CET 2009
Hi,
Steffen Müller schrieb:
> Hi.
>
> On 18.03.2009 21:25 Martin Kutschker wrote:
>> These variables should show the same charset. And this charset must be
>> the same as the one TYPO3 uses (note that Mysql uses the synonyms latin1
>> and utf8 while TYPO3 has iso-8859-1 and utf-8).
>>
>
> Thanks.
>
> If I use
> $TYPO3_CONF_VARS['BE']['forceCharset'] = 'utf-8';
>
> I also have to set
> $TYPO3_CONF_VARS['SYS']['setDBinit'] = 'SET NAMES utf8;'.chr(10).'SET
> CHARACTER SET utf8;';
>
> Otherwise I get ? instead of Umlauts.
>
> Why doesn't forceCharset imply the setDBinit settings?
>
this is imho dependend on your DB. If the DB is created with
default=latin this is needed, if DB is created with default=utf8, it's not.
vg Steffen
More information about the TYPO3-dev
mailing list