I got Backups from the ISPConfig-Menu...now, if i want to reimport the mysql-data I get wrong ä ö ü and so on...UEStudio shows me the files correct, but after import the text is wrong...please, what do I have to do to get the backup imported correctly in phpMyAdmin... Well, actually its maybe something else...even a normal html-page puts ä ö ü away on the page! So there must something wrong with the new setup etch-configuration!??
Ok, this might have been the reason: in apache2.conf I enabled the line: Code: [SIZE=1] AddDefaultCharset ISO-8859-1 [/SIZE] and in php.ini I enabled the line: Code: default_charset="iso-8859-1" Now everything seems to work right (actually the apache2.conf already did the trick....) Am I doing this right or is anything else maybe wrong with my etch-howto-installation? And is it correct, that all new databases are latin1_swedish_ci ? I'm german and not from sweden but I gues that doesn't matter in this case?
There is nothing wrong with the howto. The problem is that most linux distributions switched to UTF-8 already and this is now the default in Debian too, but your website was not in UTF-8. Switching the charset is the solution that I used too for newer linux distributions. That's correct. This means that the database has the latin1 charset which is correct for europe. Does not mysql comes from sweden? Maybe that is the cause for the strange naming "latin1_swedish_ci".
hm ok, that's one deal...I also changed now all db's into utf8 (export - change - import as utf8) and then changed my.cnf for building new db's with utf8 as default...could I get any errors in that or am I on an maybe useless but at least working way?
I'am not sure if changing the databases was a good idea. This breaks many content management systems, also ISPConfig gets broken if you chnage the databse to UTF-8.
oh, well, it seems all to work...will that happen later or should i, after changing the db, now have errors would it be ok just to switch back again or shall I leave it now as it is?
