You are not logged in.
Hi.
I've upgraded my glpi 0.68.3 to 0.70.2 but i'm having a problem with the enconding.
For example, in the follow-ups i lost information every time a phrase had words with characters like ç, ã, õ the rest of the follow-up description disappears.
If i have a follow-up with this phrase "Fazer manutenção do pc" , in glpi 0.70.2 I'll have "Fazer manuten". The rest of the descriptions disappers even in the database.
In the past, i've upgraded from glpi 0.65 to 0.68.2 and from 0.68.2 to 0.68.3 and i've never had this problem before.
Does anyone knows how to solve this problem?
thanks in advance,
Rui
Offline
Please, please, please : http://glpi-project.org/forum/viewtopic.php?id=10279
JMD / Jean-Mathieu Doléans - Glpi-project.org - Association Indepnet
Apportez votre pierre au projet GLPI : Soutenir
Offline
Please, please, please : http://glpi-project.org/forum/viewtopic.php?id=10279
More details:
- Attempt to migrate from glpi 0.68.3 to 0.70.2
- database encoding: latin1_swedish_ci
- MySQL 5.0.44
- Apache 2
- PHP 4
- OS: Linux gentoo 2.6
- browser: firefox
It seems the problem is caused by the database original encoding (latin1).
I've tried this howto http://gentoo-wiki.com/TIP_Convert_lati … 8_in_MySQL
but the follow-ups descriptions were with weird characters in place of the characters like ç, ã, õ, etc...
Any ideas?
thanks,
Rui
Offline
The update process 068 to 070 realize a full conversion in UTF8 for the DB.
It's a heavy action but at the end you have a full UTF8 DB and application.
So you don't have to do other actions like converting latin or other...
If you have problem with encoding, it was probably due to a bad update.
Please try again with your original DB but before be sure to let PHP have sufficient ressources to do the udpate action (memory limit, timeout etc...).
JMD / Jean-Mathieu Doléans - Glpi-project.org - Association Indepnet
Apportez votre pierre au projet GLPI : Soutenir
Offline
I have:
memory_limit = 128M
default_socket_timeout = 60
max_input_time = 60
I also tried with :
memory_limit = 256M
default_socket_timeout = 240
max_input_time = 240
Are these values sufficient? In the GLPI upgrade page it doesn't specify any values.
thanks,
Rui
If you have problem with encoding, it was probably due to a bad update.
Please try again with your original DB but before be sure to let PHP have sufficient ressources to do the udpate action (memory limit, timeout etc...).
Last edited by rfernandes (2008-05-15 12:01:30)
Offline
The value depends of the size of your DB .... 10 MO 1GO etc ?
It's impossible to specify a value.
JMD / Jean-Mathieu Doléans - Glpi-project.org - Association Indepnet
Apportez votre pierre au projet GLPI : Soutenir
Offline
The value depends of the size of your DB .... 10 MO 1GO etc ?
It's impossible to specify a value.
Well, I've tried with:
max_execution_time = 500
memory_limit = 254M
and my database has 7MB.
I've checked the database and there were no errors.
Can the problem be caused by other things than memory and timeout? Did someone had this problem before?
thanks,
Rui
Last edited by rfernandes (2008-05-15 13:06:16)
Offline
I was looking at php.ini and i found this commented lines
[iconv]
;iconv.input_encoding = ISO-8859-1
;iconv.internal_encoding = ISO-8859-1
;iconv.output_encoding = ISO-8859-1
Should i change them to
[iconv]
iconv.input_encoding = UTF-8
iconv.internal_encoding = UTF-8
iconv.output_encoding = UTF-8
I'm out of ideias so if anyone has any suggestion it would be great.
Thanks,
Rui
Offline
What is the charset in your php.ini ?
Do you have make manual entries or with other software than GLPI in your DB before the update ?
JMD / Jean-Mathieu Doléans - Glpi-project.org - Association Indepnet
Apportez votre pierre au projet GLPI : Soutenir
Offline
What is the charset in your php.ini ?
Do you have make manual entries or with other software than GLPI in your DB before the update ?
I've never made manual entries or any other kind in the DB.
My php.ini has the default_charset commented like this-> ;default_charset = "iso-8859-1"
Maybe i have to uncomment and force to utf-8 like this? -> default_charset = "UTF-8"
Thanks,
Rui
Last edited by rfernandes (2008-05-16 11:12:04)
Offline
Just tried upgrading glpi with default_charset = "UTF-8" in php.ini but it didn't worked
Offline
I've tried upgrading from GLPI 0.68.3 to 0.70.2 with a fresh database (that only has a ticket and a follow-up) and I got the same problem, the phrases with accents disappear.
Maybe it's something with the mysql but i've tried in 2 pc's with different versions of mysql and got the same results.
Any ideas?
Offline
send us you database. we could try the update process on our computers.
MoYo - Julien Dombre - Association INDEPNET
Contribute to GLPI : Support Contribute References Freshmeat
Offline
send us you database. we could try the update process on our computers.
Hi again,
I've installed a fresh glpi 0.68.3 with a database named "glpi" and then unpacked glpi 0.70.2 and installed it. After that, I've restored my old glpi 0.68.3 database in the glpi 0.70.2.
Now the tickets and follow-ups don't have problems with the accents but its a strange way to upgrade.
--
Rui
Last edited by rfernandes (2008-05-19 11:57:16)
Offline
the normal way : install 0.68.3 / restore your 0.68.3 database / unpack 0.70.2 and update to it
MoYo - Julien Dombre - Association INDEPNET
Contribute to GLPI : Support Contribute References Freshmeat
Offline
the normal way : install 0.68.3 / restore your 0.68.3 database / unpack 0.70.2 and update to it
The normal way you suggested didn't worked so i tried with success some extra steps on your recommendation.
So on the server with glpi 0.68.3 I did the following (as you recommended):
- dump database
- unpacked glpi 0.70.2
- update
Since the database had some problems with accents I did the following "extra" steps:
- restored the 0.68.3 database in the installed glpi 0.70.2
- updated again (and now it seems everything is ok)
Offline
you find a solution so there is no problem
MoYo - Julien Dombre - Association INDEPNET
Contribute to GLPI : Support Contribute References Freshmeat
Offline