Patch from 3.1.2 to 3.1.6 @ Ubuntu, broken text window

[koki]

Hi,

somewhere on the internet i saw a recommendation about patching from 2.4.1 to 2.4.4, and it only contained instructions to unpack the tarball to the otrs folder.

I applied the same principle to 3.1.2, but this did not change anything, and in the bottom left corner there still is "Powered by OTRS 3.1.2".

Any ideas? Do i need to follow the upgrade guide even if doing a patch?

Thanx

PS: i tried to upgrade by following the upgrade guide at first, but either i messed up, or there is something stuck in my system.

--------------

EDIT: I applied the patch, system now shows version 3.1.6, but the message box for entering tbe body of the ticket has disappeared.

picture:


Any ideas?

I extracted the tarball of otrs 3.1.6 to old OTRS directory, keeping apache2 launch script, ZZZAuto.pm and Config.pm .

[CSL]

If you're just doing a patch-level update, and have no customized files (beyond Config.pm and ZZZAuto.pm) then unpacking the tarball over the current dir should work OK (i'd still backup the whole dir first, of course).

The number at the bottom probably hasn't changed because it's cached, either in your browser or by OTRS itself. Run /opt/otrs/bin/otrs.DeleteCache.pl to flush OTRS's cache, and clear your web brower's cache as well to make sure this isn't the case.

[koki]

I deleted the cache (client and server), even restarted the apache2 process, and the bottom left text stating the version still displays 3.1.2.
Is there any (other) way to detect the version of running OTRS installation?

Thanx.

Sure, i made a backup. I'm currently trying to patch a cloned virtual machine, so this is just a test environment. Once i get it working i'm going to apply the process to the real machine

[CSL]

The version number should change; I'm pretty sure I've had this issue before where it didn't seem to. I remember the issue was a caching problem. One completely sure-fire way to discount this is to go into sysconfig, and find:
Framework -> Core::Web - Loader::Enabled::CSS
Framework -> Core::Web - Loader::Enabled::JS

(Only do this on test systems!)

Turn them both to 'off', apply, navigate back to the dashboard, and hit Ctrl-F5 to refresh without any cache whatsoever. If the version doesn't change, then the dtl files haven't been changed, which means something hasn't gone right when copying the files over.

[koki]

Although it did not directly help, it pointed me torwards the issue. I have patched the system now, but i have ran into a new problem, which i have described in the original post

[CSL]

Ok - was it a caching problem?

Try running /opt/otrs/bin/otrs.RebuildConfig.pl to see if it fixes this new issue.

[koki]

It helped, thank you very much