Your database is in latin1, and you’re trying to set the character set to utf8. You can’t do that. They have to match.
shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect |
github |
splittingred.com
If you’d like to convert your MODx database to utf8, there’s a utility here to do that:
http://bobsguides.com/convert-db-utf8.html
I’ve had a lot fewer charset problems after converting my DBs to utf8.
In PhpMyAdmin, did you check the character set of the DB, the Tables, and the text Fields in each table? Setting the Collation to utf-8 won’t change those if the data in the tables is Latin1.
Looking at the tables in the database, they are all labeled utf8-general.
Whoops, as I look at the bottom where it says 62 tables... it does say latin_swedish_ci. If I select latin_swedish_ci when doing the upgrade, would that cause any problems?
Quote from: apmkk at Jul 26, 2010, 11:49 AM
Looking at the tables in the database, they are all labeled utf8-general.
Whoops, as I look at the bottom where it says 62 tables... it does say latin_swedish_ci. If I select latin_swedish_ci when doing the upgrade, would that cause any problems?
I’ve always found I’m a lot happier if *Everything* is set to the same charset, whether it’s utf8 or Latin1. Otherwise, every time you have a problem of any kind, you wonder if it might be caused by mismatched charsets. I would never want tables in a DB to use more than one charset.
If it were my site, I’d back up the site, run the conversion utility I provided the link to above, and set everything to utf8. Just my $.02.