Thread

Nicolas, are you still having these issues? I just checked http://www.upr.biophys.kyoto-u.ac.jp/index.php/members/ and everything appears as it should?

Yes, everything is fixed, but after spending some time fixing everything manually:

From the remote server with a vanilla install of EE, I deleted all database rows in each table (without dropping the table itself), then inserted the rows from my local database (without instructions to drop table first). For some tables, I also manually created table fields (like for exp_weblog_data). This resulted in an utf8_general_ci database with utf8_general_ci tables, with utf8_general_ci fields. I could log into the CP on the remote server without any problems after that.

Since some custom field labels were stored as gibberish in the local database (displayed fine in the CP), that gibberish was carried over to the remote server. I then simply copied/pasted the correct text over the garbled text in the remote server CP, and everything was then displayed correctly the CP (and in some sections on the site). I doubt much could have been done beyond that (how could I automatically convert the gibberish to unicode characters in the local database anyways?).

Complicated and time-consuming, but it did the trick.

Luckily, the site was small enough to carry all of this out, although it was a bit tedious. I wonder what could have been done for a much bigger site. My best guess is to plan ahead and check if the production server absolutely requires utf8 before starting developing a site locally with a latin1 charset.

Glad you were finally able to get things up and running again. We appreciate your patience. Don’t hesitate to post again as needed.