[TYPO3-dev] Weird Upgrade Problem 4.1.x -> 4.2.x

[ben van 't ende [netcreators]]

Peter Russ wrote:
> On a system a new customer asked us to upgrade we experience weird
> upgrade problems with Mysql:
> MySQL 5.0.51 running on utf-8
> 
> Before update we get Umlaute displayed in sys_template
> When updating lot of sys_template fields get converted from blob to
> something more specific. By that Umlaute get's lost, i.e. the template
> get trunicated at the first occurrance of an Umlaut.
> 
> We tried to fix by exclude the sys_template fields from upgrade. That
> helps a little because fields in other tables are also converted from
> blob to something. And we experience the same problem there.
> 
> So to make it short:
> Is there parameter that we can add to setInitDB to enable clean transfer
> from blob to any other required type?
> 
> Thanks in advance. Peter
> 
> 
Hey Peter,

We use these settings. setInitDB is one of them. This is an excerpt from our
manual for converting from latin1 to utf-8 so it might not be exactly what you
are looking for.



install tool (localconf.php)

String. Normally the charset of the backend users language selection is used. If
you set this value to a charset found in t3lib/csconvtbl/ (or "utf-8") the
backend (and database) will ALWAYS use this charset. Always use a lowercase value.

$TYPO3_CONF_VARS['BE']['forceCharset'] = 'utf-8';

String (textarea): Commands to send to database right after connecting,
separated by newline. Ignored by the DBAL extension except for the 'native' type!

$TYPO3_CONF_VARS['SYS']['setDBinit'] = 'SET NAMES utf8;'.chr(10).'SET CHARACTER
SET utf8;';

String (textarea): Commands to send to database right after connecting,
separated by newline. Ignored by the DBAL extension except for the 'native' type!

$TYPO3_CONF_VARS['SYS']['t3lib_cs_convMethod'] = 'iconv';
$TYPO3_CONF_VARS['SYS']['t3lib_cs_utils'] = 'iconv';

gRTz

ben
-- 
netcreators :: creation and innovation
www.netcreators.com -  www.TYPO3.nl