Thread

While I am waiting on being able to upgrade, I am trying to at least make sure everything is ready for it. I seem to recall there is a change in the default encoding?

The site is predominantly English but with some Swedish. Right now, I set the charset of my templates to iso-8859-1 in the meta tags. I also have the xml character encoding for each weblog set to iso-8859-1. The database has the following settings:

character_set_client   | latin1
character_set_connection | latin1
character_set_database   | latin1
character_set_filesystem | binary
character_set_results   | latin1
character_set_server   | latin1
character_set_system   | utf8    

What’s the best approach to take to prepare for upgrading to avoid encoding issues with extended characters? Do I change my templates and the weblog settings to utf-8 right off, even though the database is iso-8859-1? Do I ask my host to convert the database before I upgrade to 2?

The upgrade process will take care of the conversion for you.  If you’re really nervous about it, I’d recommend running through it in a dev environment to see what you’ll need to deal with after.

I would not recommend touching the database blindly. =)

So the best approach is generally to leave as-is for now, both the database and the templates?

Does the upgrade also change the weblog/channel settings? I imagine templates need a mass edit, though.

The upgrade takes care of everything with the UTF-8 conversion.  It’s actually one of the most intensive parts of the upgrade process.

Alright, I’ll mark that one off the list of necessary preparations then, thank you. 😊

Back to eyeing shiny new add-ons for 2.x that I can’t get yet. 😉