hi all,
i'm short before being driven mad. i've got an installation of 1.3.3 running since a while. by copying the databases between localserver and productionserver i somehow messed the bloody stuff up. looks like everything after a german umlaut is cut off and not even stored in the database.
so i thought, alrighty mate, take an old proper backup and replace the bloody stuff. but same problems.
doesn't seem to be a problem of phpwcms, but the database or phpmyadmin. the backupscript still contains all german umlaute, but after importing them, everything beginning from the position of each umlaut is lost.
i wonder wether anyone came across a similar problem?
thanks in advance
ps: the complete page is broken. but the worse - the same problem may occur again and again if i'm not able to find the reason.
SOLVED - Lost content - german umlaute - charset-problem?
SOLVED - Lost content - german umlaute - charset-problem?
Last edited by kolja on Sun 9. Sep 2007, 13:42, edited 1 time in total.
hi both of you,
charset in phpwcms is utf-8 and utf8_unicode_ci. as far as i remember it worked quite well for a while.
the page is accessible via http://www.perfectbluesky.de/oz - you'll find everything ripped over there. but the problem seems not to occur in frontend. it seems like the data is already broken in the database. or perhaps phpmyadmin gives the wrong output, too.
i've got a proper backup-script containing umlaute usw. but after importing it into the database via phpmyadmin the data is lost. collation in the script is set to utf8_unicode_ci, too.
charset in phpwcms is utf-8 and utf8_unicode_ci. as far as i remember it worked quite well for a while.
the page is accessible via http://www.perfectbluesky.de/oz - you'll find everything ripped over there. but the problem seems not to occur in frontend. it seems like the data is already broken in the database. or perhaps phpmyadmin gives the wrong output, too.
i've got a proper backup-script containing umlaute usw. but after importing it into the database via phpmyadmin the data is lost. collation in the script is set to utf8_unicode_ci, too.
PROBLEM SOLVED
alrighty. problem solved. problem lies in encoding of sql-file and import-algorithm of phpmyadmin. choosing latin1 instead of utf8 on import solves the problem.