[horde] upgrade from 3.3.11 to 5.0.2

[Ralf Lang]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>> Thanks as well for any suggestions on the best upgrade path for
>>> data integrity.
>> 
>> You can directly upgrade to H5, but the H3->H4 upgrade
>> instructions still apply.
> Thanks for the quick reply,
> 
> When you say the H3->H4 instructions still apply, do you mean only
> the configuration file changes or does that include the
> horde-migrate-db script (which does not seem to be present in H5)?
> Is it possible that upgrading the long way H3->H4->H5 would produce
> a better DB migration, and therefore help situations like the one
> above?
> 
> Regards, Cale
> 
Actually it is not that easy to install a new H4 out of pear these
days. You can savely upgrade to Horde 5.

Don't forget: Horde 3 uses local timezone instead of UTC by default
AND Horde 3 does use local charset (mostly latin1) instead of UTF8.
For porting to Horde 4 or 5,

Either set the database configuration and kronolith settings right or
convert your data before.

You also should not copy-and-paste prefs and hooks without looking. A
lot of prefs have been renamed or even disappeared. The Hooks format
has changed.

http://www.ralf-lang.de/2011/06/01/migrating-horde-3-to-horde-4-top-6-ways-to-mess-up/



- -- 
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: lang at b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlDusw0ACgkQCs1dsHJ/X7DUQwCgukj/I2KBoXIoi3KSqiMfHXMr
Ri4AnjY2joZplrunpwXYzK5GtB5MP4vv
=zh9M
-----END PGP SIGNATURE-----