Upgrading from 2.1.4 to 2.2.6 seems to have broken char encoding
Before: mysql database (in latin1) shows: Réponse Automatisée OTRS webpage shows: Réponse Automatisée After Upgrade: mysql database (in latin1) shows: Réponse Automatisée OTRS webpage shows: Réponse Automatisée Any thoughts? I noticed en.pm was not updated but I tried en.pm.rpmnew as well. Thanks.
I'd love to hear any feedback on this issue if anyone has any, given that I've experienced the same issue. I'm currently still running 2.1.4 and not updating as this bug makes it impossible for us to the OTRS for all of our non-English support. Thanks in advance. From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Hiren Joshi Sent: 03 April 2008 12:54 To: otrs@otrs.org Subject: [otrs] Upgrading from 2.1.4 to 2.2.6 seems to have broken charencoding Before: mysql database (in latin1) shows: Réponse Automatisée OTRS webpage shows: Réponse Automatisée After Upgrade: mysql database (in latin1) shows: Réponse Automatisée OTRS webpage shows: Réponse Automatisée Any thoughts? I noticed en.pm was not updated but I tried en.pm.rpmnew as well. Thanks.
Hi Mustaqil,
I’d love to hear any feedback on this issue if anyone has any, given that I’ve experienced the same issue.
I’m currently still running 2.1.4 and not updating as this bug makes it impossible for us to the OTRS for all of our non-English support.
Thanks in advance.
*From:* otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] *On Behalf Of *Hiren Joshi *Sent:* 03 April 2008 12:54 *To:* otrs@otrs.org *Subject:* [otrs] Upgrading from 2.1.4 to 2.2.6 seems to have broken charencoding
Before:
mysql database (in latin1) shows: Réponse Automatisée
OTRS webpage shows: Réponse Automatisée
After Upgrade:
mysql database (in latin1) shows: Réponse Automatisée
OTRS webpage shows: Réponse Automatisée
Any thoughts?
I noticed en.pm was not updated but I tried en.pm.rpmnew as well.
Thanks.
Did you check the Charset default in Kernel/Config.pm to verify it is using the correct Charset for writing to your DBMS, after the upgrade? Alternatively it could be configured in your Sysconfig. ((enjoy)) -- Shawn Beasley ((otrs)) :: OTRS AG :: Norsk-Data-Straße 1 :: 61352 Bad Homburg Fon: +49 (0) 9421 56818 0 :: Fax: +49 (0) 9421 56818 18 http://www.otrs.com/ :: Communication with success! Geschäftssitz: Bad Homburg Amtsgericht Bad Homburg, HRB 10751 Steuernummer: 003/240/97521 Aufsichtsratsvorsitzender: Burchard Steinbild Vorstandsvorsitzender: André Mindermann
Hi Shawn, Well, I've checked the Config.pm on a development machine I have, and it's using UTF-8 for DBMS writes. As for the live system, having had checked the Config.pm on there, there is no line specifying a character encoding which strikes me as somewhat weird. However, this live system works fine with English, Japanese, Russian, Chinese, Korean and other such languages. Having had then updated the 2.1.4 Config.pm to explicitly use utf-8 no problems were encountered from viewing the ticket under 2.1.4. The problems persisted on 2.2.6 though. (2.2.6 has read access to the live system DB, but can't write to it). If 2.2.6 won't be able to read any standard answers, old tickets or any other information (this includes usernames) from our usage via 2.1.4, this proves problematic. - Muz
-----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Shawn Beasley Sent: 09 April 2008 15:39 To: User questions and discussions about OTRS.org Subject: Re: [otrs] Upgrading from 2.1.4 to 2.2.6 seems to havebroken charencoding
Hi Mustaqil,
I’d love to hear any feedback on this issue if anyone has any, given that I’ve experienced the same issue.
I’m currently still running 2.1.4 and not updating as this bug makes it impossible for us to the OTRS for all of our non-English support.
Thanks in advance.
*From:* otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] *On Behalf Of *Hiren Joshi *Sent:* 03 April 2008 12:54 *To:* otrs@otrs.org *Subject:* [otrs] Upgrading from 2.1.4 to 2.2.6 seems to have broken charencoding
Before:
mysql database (in latin1) shows: Réponse Automatisée
OTRS webpage shows: Réponse Automatisée
After Upgrade:
mysql database (in latin1) shows: Réponse Automatisée
OTRS webpage shows: Réponse Automatisée
Any thoughts?
I noticed en.pm was not updated but I tried en.pm.rpmnew as well.
Thanks.
Did you check the Charset default in Kernel/Config.pm to verify it is using the correct Charset for writing to your DBMS, after the upgrade? Alternatively it could be configured in your Sysconfig.
((enjoy))
-- Shawn Beasley ((otrs)) :: OTRS AG :: Norsk-Data-Straße 1 :: 61352 Bad Homburg Fon: +49 (0) 9421 56818 0 :: Fax: +49 (0) 9421 56818 18 http://www.otrs.com/ :: Communication with success!
Geschäftssitz: Bad Homburg Amtsgericht Bad Homburg, HRB 10751 Steuernummer: 003/240/97521
Aufsichtsratsvorsitzender: Burchard Steinbild Vorstandsvorsitzender: André Mindermann
Hi, Ali, Mustaqil M a écrit :
The problems persisted on 2.2.6 though. (2.2.6 has read access to the live system DB, but can't write to it). If 2.2.6 won't be able to read any standard answers, old tickets or any other information (this includes usernames) from our usage via 2.1.4, this proves problematic.
I have the same problem like you. I have try a upgrade from 2.1.8 to 2.2.6 on a backup machine. I have on the 2.1.8 machine and on the 2.2.6 the same in Config.pm: $Self->{'DefaultCharset'} = 'utf-8'; The 2 database have the same configuration interclassement: latin1_swedish_ci before the upgrade ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ De : Séverine Boyer À: "Support EII (informatique) Sujet: Ecran - PC 'Manip Refroidissement Rapide (Micro-four)' Créé: 08.04.2008 09:20:02 Bonjour, depuis plus d'un mois, le stagiaire travaillant sur le PC 'Manip Refroidissement Rapide (Micro-four)' rencontre des problèmes avec l'écran. Pouvons-nous, s'il-vous-plaît, résoudre ce problème ? En vous remerciant, +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ after the upgrade: De: Séverine Boyer À: "Support EII (informatique)" Sujet: Ecran - PC 'Manip Refroidissement Rapide (Micro-four)' Bonjour, depuis plus d'un mois, le stagiaire travaillant sur le PC 'Manip Refroidissement Rapide (Micro-four)' rencontre des problèmes avec l'écran. Pouvons-nous, s'il-vous-plaît, résoudre ce problème ? En vous remerciant, Séverine A.E. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ A new created ticket is correct with the accent: +++++++++++++++++++++++++++++++ De: Serge.Algarotti À: Autres Sujet: essai 2.2.6 Créé: 09.04.2008 17:22:04 essai 2.2.6 éèàù ++++++++++++++++++++++++++++ Best regards -- Serge ALGAROTTI [http://www.cemef.ensmp.fr/] Ecole des Mines de Paris-CEMEF UMR CNRS n° 7635
Hi, Serge ALGAROTTI a écrit :
Hi,
Ali, Mustaqil M a écrit :
The problems persisted on 2.2.6 though. (2.2.6 has read access to the live system DB, but can't write to it). If 2.2.6 won't be able to read any standard answers, old tickets or any other information (this includes usernames) from our usage via 2.1.4, this proves problematic.
I have the same problem like you. I have try a upgrade from 2.1.8 to 2.2.6 on a backup machine.
I think , i have found the problem in the mysql database in v 2.1.8, we have in the a_content_type: text/plain, charset=iso-8859-15 in the mysql database in v 2.2.6, we have in the a_content_type: text/plain; charset=utf-8 How can convert the old databse in the new type ? Serge
Hi,
The problems persisted on 2.2.6 though. (2.2.6 has read access to the live system DB, but can't write to it). If 2.2.6 won't be able to read any standard answers, old tickets or any other information (this includes usernames) from our usage via 2.1.4, this proves problematic.
I have the same problem like you. I have try a upgrade from 2.1.8 to 2.2.6 on a backup machine.
I found the solution: I have the problem with a dump of the mysql database when it's done with phpMyadmin. I have no problem when the dump is done with mysqldump Serge
participants (4)
-
Ali, Mustaqil M -
Hiren Joshi -
Serge ALGAROTTI -
Shawn Beasley