Hi Mike,
I get that, but my upgrading procedure might be a little off. I do it like this:
1. unpack the new otrs in a new directory, like otrs-3.0.5
2. Copy over files from the running installation (the configuration mentioned in the UPGRADING file)
3. shut down everything
4. switch directories so the new installation is in otrs and the old is in otrs-3.0.4
5. run SetPermissions
6. Fire up everything
I'm a little reluctant to unpack the new version on top of the old one, as the UPGRADING file suggests. If something goes wrong in the above steps, all I need to do is rename two directories and restart Apache to be back on the old version. But it has some drawbacks I haven't figured a way around yet - especially because it breaks all installed packages.
Maybe the UPGRADING file needs an overhaul to make people able to quickly perform a roll-back in case of errors. Rollback will probably only be possible on patch releases with no database changes, but it is nice to have that option. The UPGRADING file should also cover patch release upgrading.
Lars
From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Michiel Beijen
Sent: Monday, February 14, 2011 4:07 PM
To: User questions and discussions about OTRS.
Subject: Re: [otrs] Strange behaviour in SysConfig after upgrade to 3.0.5
If you use a custom theme, you should **only** copy over the dtl files that you actually modify. This should also have prevented you from this particular issue.
--
Mike
On Mon, Feb 14, 2011 at 3:37 PM, Lars Jørgensen
