Upgrade 3.1.10 to 3.2.1 - JS error on login

[gars]

Good morning.
I'm having problems on upgrade from 3.1.10 to 3.2.1.

Following manual, UPGRADE section:
- Backup and restore of config files - done OK.
- Permissions - done OK.
- Database scripts, done OK
- RebuildConfig, DeleteCache, done OK.
Obs: There are missing steps on documentation about backup and restore language files. Without this, several errors occurs.

Before first login on browser, on page load, I got this javascript message alext:
"Namespace Core.UI.Datepicker could not be initialized, because jQuery UI datepicker could not be found."

Firefox debugger shows this detail:
"Error: uncaught exception: Namespace Core.UI.Datepicker could not be initialized, because jQuery UI datepicker could not be found."

"Error: TypeError: Core.App.Ready is not a function
Source: http://otrsserver/otrs/index.pl
Line: 236"

System envroinment:
Linux Debian Squeeze, kernel 2.6.32-5-686
Apache 2.2.16
Database PostgreSQL 8.4.13

Does anyone know how to solve this issue?

[crythias]

Your apache log files will tell you where it's looking for these files. It appears that you've installed the new release not over or a replacement for your old one.

[gars]

Hi crythias.
You're right about install...
I hold the old install as /opt/otrs-3.1.10 install intact. I decompressed tar.gz package into /opt/otrs-3.2.1 and then created a symbolic lynk /opt/otrs pointing to /opt/otrs-3.2.1, not to ovewrite the original install. And then restored all backup files as told in the admin manual.

So, the correct upgrade install is to overwrite the old install (only after backuping config files, etc)?
It was not clear for me.

Thanks.

[crythias]

So, the correct upgrade install is to overwrite the old install (only after backuping config files, etc)?

It is possible and suggested to do what you want as a fresh install and then copy your config (and possibly filesystem attachments, if so configured) over to the fresh install.
On the other hand, it may be easier to back up and overwrite your production install, run updates, clear cache, rebuild config.

It's all about your tolerance level and recoverability in case things go bad.

Creating and symlinking to a fresh install is "most likely to work" and "least likely to destroy" but if you have code customizations, you'll need to know how they'll be affected by either choice.