Comments on: Can Anyone Help me Save my Chinese Blog?

By: Mark

Mark — Mon, 16 Jul 2007 09:05:56 +0000

I think Stephan has pretty gotten it fixed for me. Thanks, everybody.

By: Scott

Scott — Mon, 16 Jul 2007 03:19:19 +0000

If you havent been able to fix this yet. Zip your backup database sql file and post a link to it here and I will update it so it will work for you.

By: Stephan

Stephan — Tue, 03 Jul 2007 06:53:03 +0000

I should mention, it’s “my web site” that I’m talking about in previous post. I don’t have access to yours.

By: Stephan

Stephan — Tue, 03 Jul 2007 06:51:48 +0000

OK,

I’ve successfully imported the wp_comments table into my local MySql database using phpMyadmin.

Well, actually, I only imported the first couple hundred records. I’ve sent you a private email to your gmail account. Please read it as soon as you can.

What I ended up doing (so far) is probably overkill, so I’ve still got to reduce the number of steps. Basically, I made a new table (different encodings, etc.) to see if that would help. Using “Import”, it did NOT help, but if I run the sql Insert commands from the command window, they all work fine.

So, the file upload/import step is where the data gets corrupted.

I’m going to upload the file to the web site, and import direct from there next to see if that also allows a quick fix.

Do you have phpMyAdmin? Do you have shell access and ability to run mysql from the command line?

By: Stephan

Stephan — Mon, 02 Jul 2007 05:22:57 +0000

Well, now I think I was wrong about the EN-US. I see that’s part of the browser ID that you’re storing.

By: Stephan

Stephan — Mon, 02 Jul 2007 05:12:28 +0000

I’ve looked at the “backup”. Now I see that it wasn’t done by phpmyadmin. The latin-1 is only a “default” for the table, but it should be changed anyways. However, I think the REAL problem is that every data (insert) line is encoded with en-US.

Tomorrow is last day of finals. After that, I’m going to try and load directly with phpMyAdmin after changing the encoding of the inserts.

By: Mark

Mark — Sun, 01 Jul 2007 21:17:31 +0000

Fili, your comment was caught by Akismet. That’s why I missed it. Thanks for the ideas. Unfortunately, my backups were created by Dreamhost via their panel. I have some of my own, but they’re really old and missing over a hundred comments. Maybe I’ll just start over.

Hmm… the rolling archives are part of the K2 theme. The strange thing is that all that stuff still loads when I switch back to my old theme. I think the drop-down archives in my sidebar may be the culprit!

By: Mark

Mark — Sun, 01 Jul 2007 13:15:28 +0000

I have tried removing all the “latin-1″s from the file, Stephan. The import fails. I also tried just doing a search and replace via a text editor to change all the “latin-1″ tags into UTF8.

I really appreciate your suggestions, though. I’m really not much of an SQL guy at all.

By: Stephan

Stephan — Sat, 30 Jun 2007 01:55:25 +0000

Have you tried just removing the latin-1 “hints” from the script? You shouldn’t need them, as it should just take the database default if you don’t.

Otherwise, perhaps the “Utf8″ tag is incorrect. I assume you’re using phpMyAdmin to do the import also?

I’ll look at the script today too, and try it out on my server…

By: fiLi

fiLi — Wed, 27 Jun 2007 16:37:16 +0000

I’m sorry, but I think this has nothing to do with your import, but rather with your export. This file is corrupted …

I tried it, and repaired the SQL tables through this little trick here - http://www.filination.com/tech/2007/04/27/drupal-change-db-and-table-collation-to-unicode-utf-8/

but I already suspected the file doesn’t look right.

Do you have a gziped SQL backup file that hasn’t been exported through phpmyadmin?

Since you only have a few posts, you can do what you already did before - use the Google Archive to restore everything. It will take an hour or so, but…

As for load time, use OctaGate (http://www.octagate.com/service/SiteTimer/) and Web Page Analyzer (http://www.websiteoptimization.com/services/analyze/) to see what’s taking so long.
The index page reports “” which is insane.
For example, you can see that “rolling archives” - whatever that is - is loading all your archives every single time, etc.