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

10 Apr 2008

      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