Comments on: Optimising Grandad

By: Kirk M

Kirk M — Tue, 04 Aug 2009 16:15:41 +0000

Head Rambles being about the same age as my effort I would have to believe that your WP DB tables originally started out as Latin-1 like mine did. And when I had to rebuild JT I did some hunting around and found out that going into my MySQL DB tables and dumping them all using an UTF8 format wasn’t enough. I ended up having to manually convert each table to UTF8 as well which I actually accomplished on the old site before I cleaned things up and imported them over to the new site (and more cleaning before going live).

This is Alex King’s post where I got the instructions from (not only from the post itself but I had to read down the comments as well before I understoof what to do).

http://alexking.org/blog/2008/03/06/mysql-latin1-utf8-conversion

Not that you’ll want to start mucking around again but this can be done on a live site, you just have to take it down for a bit during the re-import when your done converting.

Of course if you’ve already done this…please disregard.

By: Maxi Cane

Maxi Cane — Fri, 31 Jul 2009 12:28:42 +0000

Have you tried just calling a man who charges too much to do it for you?

I do that with everything.

By: Baino

Baino — Fri, 31 Jul 2009 09:33:34 +0000

Ah that explains why you’re not coming up in my reader!

By: Richard

Richard — Thu, 30 Jul 2009 14:15:51 +0000

Welcome Darragh! Both are on the same VPS and phpMyAdmin is installed. The coding, as I said is the same on both.

Update:
I tweaked the .htaccess file and managed to copy the contents across using the XML export/import. The problem persistes!!

By: Richard

Richard — Thu, 30 Jul 2009 13:48:43 +0000

Andrew: The first thing I thought of when I saw those characters was the encoding. Both however are set to UTF-8. This is what has me baffled!

As for the too large file – it won’t recognise a zipped file. It has to be XML.