Broken accented words after 0.68.3 => 0.70.20

tomascohen · 2008-04-13 11:53:56

After doing the upgrade through the documented steps (i.e. "Unpack the new archive and overwrite all files of the old version") I get every accented sentence cut and thus being useless.

Accents appear perfectly in menus, but knowledge base, infos, and issues are all broken.

Any clues?
Thanks

JMD · 2008-04-13 14:55:08

Please...

http://glpi-project.org/forum/viewtopic.php?id=5651

tomascohen · 2008-04-13 19:46:04

* I use 0.68.3 version of GLPI, and trying to update tu 0.70.2
* It is actually installed in a Gentoo Linux (x86_64) with this software versions:
* GLPI was first installed using the standard procedure, and then uploaded database from a previous backup from other server with (almost, x86) the same specs.
* Apache 2.2.8 - PHP 5.2.6-rc3 - MySQL 5.0.54. I performed the upgrade from Mozilla Firefox 2.0.0.12 first, then from Mozilla Firefox 3 beta5 and Konqueror 3.5.9.
* GLPI is using IMAP authentication, provided by other Gentoo box which has Courier-IMAP 4.0.6
* I don't see any errors in debug mode (in 0.68.3 at least).
* I think there is a problem in the setup scripts that doesn't perform properly, failing to detect codifications of the fields of the DB, probably because of a broken DB. GLPI hasn't caused any trouble before, I'm actually running GLPI flawlessly from the backup now.

JMD · 2008-04-13 23:06:26

- Did you make some manual modification in your db before ? editing or other ?

- The full conversion utf8 could failed also if your db is large and your memory limit in php.ini too small (if this case you would have somme errors).

- What is your default charset that you choose in your php.ini ?

tomascohen · 2008-04-24 23:49:19

- Did you make some manual modification in your db before ? editing or other ?

How do I check sanity of the DB, is there any script to check for errors?

- The full conversion utf8 could failed also if your db is large and your memory limit in php.ini too small (if this case you would have somme errors).

memory_limit = 128M

JMD · 2008-04-25 00:16:47

And the last question ?

tomascohen · 2008-04-25 01:34:19

JMD wrote:

- What is your default charset that you choose in your php.ini ?

In php.ini I have:

;default_charset = "iso-8859-1"

which is commented so I guess it defaults to PHP's default, which I don't know. phpinfo() tells:

default_charset no value no value

and I also have

mysql.connect_charset = utf8

JMD · 2008-04-25 19:48:58

and then uploaded database from a previous backup from other server with (almost, x86) the same specs.

Which way do you follow to export and import your db in your new server ?

The mysql version of the old server is the same as the new server ?

Export conversion with mysql 4 is different from mysql5

tomascohen · 2008-04-25 21:59:00

I did

# mysqldump --opt -p glpidb > glpidb.sql

and copied through scp the entire glpi's root dir.

In both cases it's a 5.0.54 version of MySQL.

JMD · 2008-04-26 00:08:50

I think the problem could come from the export.

In 0.68.3 the charset in the db is not clean (table are annouced to be utf8 but data are in latin), when you do an mysqldump, mysql use by default the utf8 charset and it's wrong.

You could try this option :

mysqldump --default-character-set=latin1

for your export

tomascohen · 2008-04-26 00:55:58

I did that mysqldump when I moved my glpi install from one server to another a long time ago. This install has been in production flawlessly for months, so I don't know where the problem could be.

As I said, problem arise when I try to upgrade.

I there any way to check my DB for problems? (i mean, 0.68.3's DB, the working one).

Forum GLPI-Project

Announcement

#1 2008-04-13 11:53:56

Broken accented words after 0.68.3 => 0.70.20

#2 2008-04-13 14:55:08

Re: Broken accented words after 0.68.3 => 0.70.20

#3 2008-04-13 19:46:04

Re: Broken accented words after 0.68.3 => 0.70.20

#4 2008-04-13 23:06:26

Re: Broken accented words after 0.68.3 => 0.70.20

#5 2008-04-24 23:49:19

Re: Broken accented words after 0.68.3 => 0.70.20

#6 2008-04-25 00:16:47

Re: Broken accented words after 0.68.3 => 0.70.20

#7 2008-04-25 01:34:19

Re: Broken accented words after 0.68.3 => 0.70.20

#8 2008-04-25 19:48:58

Re: Broken accented words after 0.68.3 => 0.70.20

#9 2008-04-25 21:59:00

Re: Broken accented words after 0.68.3 => 0.70.20

#10 2008-04-26 00:08:50

Re: Broken accented words after 0.68.3 => 0.70.20

#11 2008-04-26 00:55:58

Re: Broken accented words after 0.68.3 => 0.70.20

Board footer