Bug #81496

Invalid Charset UTF8 at Hoster Strato

Added by Jürgen König almost 2 years ago. Updated 17 days ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-06-07
Due date:
% Done:

0%

TYPO3 Version:
8
PHP Version:
7.1
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When moving a Typo3 8.7.1 installation from hoster all-inkl to Strato I encountered an error when connecting to a new database.

"Invalid Charset
Your database uses character set "latin1", but only "utf8" is supported with TYPO3. You probably want to change this before proceeding."

This message did not occur with Typo3 7.6 and same empty new database at Strato.

After talking with Strato support and research in the internet I could solve the problem but it was quite a hassle to find a solution.
(http://www.debacher.de/wiki/Installation_von_Typo3_8.7)

It would be helpful to add some hints in the official installation guide for Typo3 8.7 (does it already exist?) or in the error message itself. It is quite confusing when using a UTF8 database and getting an error it is not a UTF8 database.

A similar problem and confusion hass occurred here: https://forge.typo3.org/issues/80733

Thank you!

screen_phpmyadmin_allinkl1.JPG View (155 KB) Jürgen König, 2017-06-07 11:17

screen_phpmyadmin_allinkl2.JPG View (293 KB) Jürgen König, 2017-06-07 11:17

screen_phpmyadmin_strato1.JPG View (165 KB) Jürgen König, 2017-06-07 11:17

screen_phpmyadmin_strato2.JPG View (338 KB) Jürgen König, 2017-06-07 11:17

screen_typo3-Installtool.JPG View (86.8 KB) Jürgen König, 2017-06-07 11:17


Related issues

Related to TYPO3 Core - Bug #80733: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) Exception while upgrading from 8.6.1 to 8.7.0 Rejected 2017-04-06
Duplicated by TYPO3 Core - Bug #87034: Fresh Install Wrong DB Connection Collation Closed 2018-11-29

History

#1 Updated by Jürgen König almost 2 years ago

Here some screenshot of the two databases at all-inkl and Strato

#2 Updated by Markus Klein almost 2 years ago

  • Related to Bug #80733: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) Exception while upgrading from 8.6.1 to 8.7.0 added

#3 Updated by Stephan Großberndt over 1 year ago

TYPO3 requires your database and your tables to be utf-8 since at least 6.2, I think even 4.7. It may have worked by chance until now with a wrong charset but with TYPO3 8.7 you really should change this.

Your first all-inkl/strato screenshots just show the database connection you are using is utf8.

Your database may are may not be UTF-8, but neither on all-ink nor on strato your tables are UTF-8 as can be seen on the second screenshots you provided - all of them have a collation of latin1_swedish_ci.

Making sure your database has a collation of utf8_general_ci is only the first step. This secures tables newly created by TYPO3 have the correct collation. If you dump tables from another database you dump the collation information with it, so just inserting your latin1_swedish_ci tables from all-ink to the strato database does not make them utf8_general_ci

Convert all of your tables to utf8_general_ci and change the database collation to utf8_general_ci, if thats not already set.

See e.g. https://wiki.typo3.org/UTF-8_support#Convert_an_already_existing_database_to_UTF-8

Apart from that: https://github.com/TYPO3/TYPO3.CMS/blob/master/INSTALL.md#mysql-environment should probably mention an utf8 charset is at least recommended if not required.

#4 Updated by Jürgen König over 1 year ago

Of course I know the UTF-8 is required for a long tim.e The funny thing is, that it worked at all-inkl with Version 7.6 and 8.7 without a warning in Install Tool. Only after moving to Strato the message occured.

Anyway the solution from http://www.debacher.de/wiki/Installation_von_Typo3_8.7 ist much easier than the solutions listed on https://wiki.typo3.org/UTF-8_support#Convert_an_already_existing_database_to_UTF-8

Maybe it would be nice to add the simple solution from debacher to your link or in the installation guidelines for 8.7.

#5 Updated by Josef Glatz 7 months ago

Stephan Großberndt wrote:

...
Apart from that: https://github.com/TYPO3/TYPO3.CMS/blob/master/INSTALL.md#mysql-environment should probably mention an utf8 charset is at least recommended if not required.

What about adding a check in the install tool or a early warning? The README part should definitely extended with the information about the default db collation

#6 Updated by Susanne Moog 17 days ago

  • Duplicated by Bug #87034: Fresh Install Wrong DB Connection Collation added

#7 Updated by Riccardo De Contardi 17 days ago

Just as a note: As far as I see in the documentation, the DB charset requirement is cited on https://docs.typo3.org/typo3cms/InstallationGuide/Troubleshooting/Mysql/Index.html

Also available in: Atom PDF