Upgrade from 1.1.3 to 2.2.2

Hello! I am new to this list, but not new to OTRS. I am running version 1.1.3 which I installed from RPM. I now wish to update to a more modern version. The UPGRADING file in the source gives instructions for updating from 2.1 to 2.2. However, I have no idea how to get to 2.1 or if that is even necessary. What should my upgrade path be? I am hoping I don't need to upgrade to every interim release. That would be a lot of work: 2.2.2 (2007-07-31) (CHANGES) 2.2.1 (2007-07-02) (CHANGES) 2.1.7 (2007-04-05) (CHANGES) 2.1.6 (2007-03-02) (CHANGES) 2.1.5 (2007-01-25) (CHANGES) 2.1.4 (2006-12-14) (CHANGES) 2.1.3 (2006-11-17) (CHANGES) 2.1.2 (2006-10-18) (CHANGES) 2.1.1 (2006-10-05) (CHANGES) 2.0.4 (2005-11-21) (CHANGES) 2.0.3 (2005-10-05) (CHANGES) 2.0.2 (2005-08-22) (CHANGES) 2.0.1 (2005-08-01) (CHANGES) 1.3.3 (2005-11-21) (CHANGES) 1.3.2 (2004-10-15) (CHANGES) 1.3.1 (2004-09-20) (CHANGES) 1.2.4 (2004-07-08) (CHANGES) 1.2.3 (2004-04-07) (CHANGES) 1.2.2 (2004-02-23) (CHANGES) 1.2.1 (2004-02-16) (CHANGES) Any help is appreciated! Dimitri -- Dimitrios Gerasimatos dimitrios.gerasimatos@jpl.nasa.gov Section 343 Jet Propulsion Laboratory 4800 Oak Grove Dr. Mail Stop 264-820, Pasadena, CA 91109 Voice: 818.354.4910 FAX: 818.393.7413 Cell: 818.726.8617

Hi, dvg schrieb:
Hello!
I am new to this list, but not new to OTRS.
I am running version 1.1.3 which I installed from RPM. I now wish to update to a more modern version. The UPGRADING file in the source gives instructions for updating from 2.1 to 2.2. However, I have no idea how to get to 2.1 or if that is even necessary. What should my upgrade path be? I am hoping I don't need to upgrade to every interim release.
I don't know your old version, but let me try... Really much work for you! * Make a backup of your otrs-db * Update you db with applying all the sql-update-scripts (you have to apply every update-file from subversion to subversion untill you reached your final version) * Make a brand new installation of you final OTRS version => now, you should have access to your data. * Customize your new version (via Config.pm and especially Sysconfig) Attention: your old system runs under iso-charset, your new on should run under utf-8. So you have to convert your DB to utf-8. Hope it helps. Bye, Alex
participants (2)
-
Alexander Scholler
-
dvg