Thanks. I am not going to do in-place upgrade. I will migrate RT from 3.2.3 on one server to 3.8.9 on another server. In this scenarios, how does upgrade doc apply?
Here is what I like to do: 1. Dump database off RT 3.2.3. 2. Install and configure RT 3.8.9 on a new server 3. Import RT database into RT 3.8.9 For this upgrade path, what are the RT and MySQL upgrades I should perform after step 3? Simon On Tue, Mar 22, 2011 at 1:59 PM, Ruslan Zakirov <[email protected]>wrote: > On Tue, Mar 22, 2011 at 10:56 PM, Simon Gao <[email protected]> > wrote: > > What's the proper steps for upgrading very old RT to up-to-date version? > > Read README and UPGRADING documents five times. > > local directory may cotain files that override things in the core and > such customizations may hide new code. This is what happened in Ulf's > case. > > > I am looking at upgrading RT from 3.2.3 to 3.8.9. > > > > Simon > > > > On Tue, Mar 22, 2011 at 12:01 PM, Kevin Falcone < > [email protected]> > > wrote: > >> > >> > Etc, plugins and po are empty, html has Elements and Ticket > >> > directories in it. Lib has a Ticket_Overlay.pm in it. As far I > >> > remember we did have someone hire someone to add something to our RT > >> > installation. I am trying to find out more about it. > >> > >> There's your problem. > >> > >> Your Ticket_Overlay.pm is killing RT's Ticket_Overlay.pm > >> > >> Remove it until you can restore it as a proper extension using either > >> Ticket_Local.pm or normal extensions. > >> > >> -kevin > > > > > > > > -- > Best regards, Ruslan. >
