Re: [otrs] Upgrading from 2.1.4 to 2.2.6 seems to have broken charencoding

[Shawn Beasley]

Hi Mustaqil,

Thanks in advance.

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. *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Hiren Joshi

*Sent:* 03 April 2008 12:54
*To:* otrs@otrs.org



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.

*Subject:* [otrs] Upgrading from 2.1.4 to 2.2.6 seems to have broken charencoding

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

signature.asc
Description: OpenPGP digital signature

_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support or consulting for your OTRS system?
=> http://www.otrs.com/