Works for me. I created a blog post and put Korean characters in the body of the post.

Cash, this person appears to be describing an upgrade situation. The characters were written in Elgg 1.6.1 or below, and then do not appear properly after the upgrade to Elgg 1.7.

Is that the scenario you tested?

No, I tested on an upgraded site with a new blog entry. I can confirm on an Elgg 1.6.1 site with Korean characters that the upgrade corrupts the database. I'll tell Dave and Brett. It looks like the 1.7 is not ready for those needing UTF-8.

I used Japanese to develop this migration and it worked ok... Looking into it now.

Ticket is here: http://trac.elgg.org/ticket/1928

If you have experienced this, any information you can provide on how your database was set up (encodings) is useful.

Hi, I want to upgrade to 1.7 elgg version on my site (with 1.6.1 elgg version). This sites is http://redes.epesca.org. When i just make the process get the following problem.

- Icon loose reference.

- The Special characters don't show on screen.

- Problem on login (via facebook or normal login).

I show a preview of versión 1.7

My problem was that I created the string in UTF8 so when the upgrade ran it assumed the string was in latin1 and converted it to garbage. My fault, not the script's fault.

kako's problem looks like the upgrade script was not run on the database.

We need details from sam to investigate any further.

Sam and Kako, did you remember to run

http://link-to-your-elgg/upgrade.php

after installing the Elgg 1.7 code?

If not, as Cash says, your Elgg database may not have been converted to UTF-8.

Do you mean "Upgrade step 3. Visit http://your-elgg-site-URL/upgrade.php"

I definitely did it.

Concerning UTF-8, when I inserted [ko.php]s (ko=Korean) into language files in Elgg 1.6.1, I have converted them all into UTF-8, because when it is not converted whole websites are broken. I think Korean characters are only working in UTF-8 environment.

After update, language files don't have any problem, but the comments that users have written in websites in Korean are broken into "???".