Horde / Turba: Umlauts not properly converted after upgrade

Created:

2016-11-16 13:09:28 UTC

Modified:

2017-08-16 16:58:06 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Horde / Turba: Umlauts not properly converted after upgrade

Applicable to:

  • Plesk 11.x for Linux

Symptoms

In Horde addressbook contacts are broken if they contain umlauts.

Cause

Root cause is in the upgrade mechanism

Resolution

Root cause is in upgrade mechanism. Horde 3 database was encoded in latin1, since Horde 5 database is encoded in utf8. Existing records should be update updated in database to new encoding; but they do not currently. Internal software issue is #PPPM-1391

To workaround the problem you can make database dump with 'latin1' encoding set and restore it with 'utf8' encoding:

Please note that this workaround should be applied ONLY in case no new entries with non-latin symbols were added to Horde address books after upgrade. Otherwise these new entries become corrupted as well.

mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` horde --default-character-set=latin1 --skip-set-charset > hordedump

mysql -uadmin -p`cat /etc/psa/.psa.shadow` horde --default-character-set=utf8 < hordedump`

If the above workaround is applicable for you, then please take the backup of all necessary databases using below commands and apply the above provided workaround:

mkdir /root/__sqlbackups
mysqldump -uadmin -p`cat /etc/psa/.psa.shadow ` psa > /root/__sqlbackups/psa.`date +%F_%H.%M`.sql
mysqldump -uadmin -p`cat /etc/psa/.psa.shadow ` mysql> /root/__sqlbackups/mysql.`date +%F_%H.%M`.sql
mysqldump -uadmin -p`cat /etc/psa/.psa.shadow ` --all-databases > /root/__sqlbackups/all.`date +%F_%H.%M
Have more questions? Submit a request
Please sign in to leave a comment.