Bug #26687: UTF-8 support is broken - TYPO3.Flow - TYPO3 Forge

TYPO3 Flow Base Distribution TYPO3.Eel TYPO3.Flow TYPO3.Fluid TYPO3.Kickstart TYPO3.Welcome Packages Applications

Bug #26687

UTF-8 support is broken

Added by Martin Brüggemann about 4 years ago. Updated about 4 years ago.

Status:

Resolved

Start date:

2011-05-06

Priority:

Must have

Due date:

Assigned To:

Karsten Dambekalns

% Done:

100%

Category:

Persistence

Target version:

TYPO3 Flow Base Distribution - 1.0 beta 1

PHP Version:

Complexity:

Has patch:

Affected Flow version:

Description

I just saved some FLOW3 objects with german umlauts and it seems that there's a "SET NAMES UTF-8" or some Doctrine2 UTF-8 connection setting missing. Also all autogenerated MySQL tables have latin1_swedish_ci collation. Should be easy to fix this.

These are my connection settings in Settings.yaml

FLOW3:
  persistence:
    backendOptions:
      driver: pdo_mysql
      host: 127.0.0.1
      port: 3306
      dbname: guruhelp_local
      user: root
      password: dasistnureinhohlespasswortdaskeinerkennt
      path: guruhelp

wrong_utf8_encoded_object.png (57.8 kB) Martin Brüggemann, 2011-05-06 22:32

Associated revisions

Revision a1c06043
Added by Karsten Dambekalns about 4 years ago

[FEATURE] Enable SQL connection initialization

Some database setups might need to run some initial SQL statement after
a connection has been established. Examples are date/time format options
for Oracle or charset settings for MySQL.

For MySQL UTF-8 support was potentially broken, depending on the system
setup. This can be fixed by using the new initialization option:
FLOW3: persistence: doctrine: dbal:
sessionInitialization: 'SET NAMES utf8 COLLATE utf8_unicode_ci'

Change-Id: I456f313014e1943733aa5d7aa9cf9c8cb20f34a8
Fixes: #26687