Umlauts broken in mysql DB after migration

[Brujo]

Hi, today i migrated 2 Domains from one Plesk Server (Ver. 8.3.0 Suse 10.1/64 mysql 5.0.51 collation utf8_general_cli) > (Ver. 8.3.0 Suse 10.2/64 mysql 5.0.51a collation utf8_general_cli)

and on both Domains one is typo3 based the other is a php based cms
are on many places the German umlauts or international signs with apostroph broken.

Any hint or idea is realy wellcome.....

 

[sonic79]

look into your browser. under which content-type is your page transmitted to your browser ?

content-type can be changed in 3 ways:
- apache config
- php config
- content files (php., .html. e.g.)

Generally content is delivered under content-type configured under apache if no content-type is given by content.

 

[Brujo]

thanks for the Hints, but there is no different in the configs between the both Server

so i did the migration again end keept the migration files (source & Destination Server) and i tried to import the created dump files from the migration manager on a Test DB and this went wrong even on the Source Server.

I did then a manuall dump and imported this dump on the new Plesk Server and everything wents fine..

So for me it looks like as an issue of the Migration Manager....

Brujo

 

[Brujo]

i did more resaech on this issue and found the following.

i checked the diff between the manual mysqldump & the dump generated from the migration manager and there is one difference in the mysql header. In the dump of the migration manager; the following line is missing: /*!40101 SET NAMES utf8 */;

if i put this line in and import the dump all characters are shown OK, and if i delete this line again and import the dump the characters are broken...

i still belive this looks like a migration manager bug... any more hints?

Brujo

 

[kuschelroboter]

i have the same Problem,
where can i find die migration-dump to change the line?

thx

Kuschelroboter

 

[Brujo]

the migration files are stored in the path which you define during the migration, but you have to switch of also compression and on the end of the migration you have to set keep temp migration files.

Brujo

 

[kuschelroboter]

Thanks for your fast answer.

is the dump one File for all Domains or is it a dump for every Domain?
how to insert the Dump into the Database? with Plesk or by Hand ?

Sorry for the Questions of a Beginner
Kuschelroboter

 

[Brujo]

depending on your selection during the migration. for example i did only a single Client migration with 3 Domains which have some DB`s. So the Dump File have separate mysql dumps which you can manually import via mysql.

 

[OZyryanov]

Could you execute next statement

SHOW CREATE DATABASE YOUR_DATABASE_NAME;

in mysql at source and destination hosts and print the results hire.

Thanks.

 

[Brujo]

soure:

mysql> SHOW CREATE DATABASE `jr-typo4`\G
*************************** 1. row ***************************
Database: jr-typo4
Create Database: CREATE DATABASE `jr-typo4` /*!40100 DEFAULT CHARACTER SET utf8 */
1 row in set (0.00 sec)

destination imported via migration manager and the umlauts in the imported tables are brocken!

mysql> SHOW CREATE DATABASE `jr-typo4`\G
*************************** 1. row ***************************
Database: jr-typo4
Create Database: CREATE DATABASE `jr-typo4` /*!40100 DEFAULT CHARACTER SET utf8 */
1 row in set (0.00 sec)

if i put this line into the migration dump and import the dump the manually all characters are shown OK.
/*!40101 SET NAMES utf8 */;

 

[sync]

for correct showing that pages in browser set the options for php-mysql client connect like this:
"mysql_query("set names 'utf8'",$connection);" in your php code.