Migrating AND upgrading at the same time is not a good idea, but I don't think that is the cause of your issue. Did you try what http://forums.b2evolution.net/viewtopic.php?t=6470 says might help?

I'm sorry but I can offer no real help here. All I know is when I backup and restore comments from ¥åßßå get all messed up and I simply go in and edit each comment to make it right again. Probably if I learn what you need to do I won't have that issue next time?

By the way the "migrate and upgrade" should not be an issue this time because I think the database had no changes from 240 to 241. Normally it is risky though because of database changes. So normally "migrate first then upgrade" or "upgrade first then migrate".

Here's hoping the other thread helps!

Thanks EJB for quick response.

I want to try iconv.
How do i know the encoding of my existing database, using phpmyadmin ?
Thanks

Tv

hmmm... the post title says [1.10.x] but your post says 2.4.0 and 2.4.1 so I hope this does not include a 1.10.x database because that will absolutely make this much worse.

Anyway I found my encoding via phpmyadmin, but not when I actually selected a database. On the first screen it is there, but once I pick a database I have to click on the top where it says "Server: localhost".

AFAIK phpMyAdmin exports database in UTF-8 by default, so when you import your db select File encoding: utf8 .

I had the same encoding problems on MySQL 4 , does the host you exporting db from use MySQL 4? :roll:

Also make sure your new db has the same collation as another one.