WordPress.org

1. pepsimax2k
   Member
   Posted 1 year ago #

   Hi, just moved a wordpress install to another host, used the wp database backup plugin to backup then imported using phpmyadmin and have ended up with a load of � (black diamond with question mark inside) characters instead of special characters (£ ' " etc).

   any idea what caused it and how to fix it? I'm hoping it's just something like character encoding in phpmyadmin (i had utf-8 selected).

   i also got the same problem after importing from greymatter (old blog) but thought it was just down the gm and not wp related :o\

   edit: when importing tables, i extracted the gz file, which saved the sql file as a gedit file in gnome/linux, then imported over firefox. any chance that could have messed up file encoding, and either importing the gz file or doing it from windows / notepad would work better?

   edit 2: from phpmyadmin:

   Collation
   latin1_swedish_ci

   well that weren't there on my other site :o|

2. pepsimax2k
   Member
   Posted 1 year ago #

   Right I fixed it. Cause was some weird character set stuff, fix is not so complicated:

   Basically it happened because I'd had one blog started from 2.1, upgraded through 2.2, then wanted to move server and started out testing a 2.1 install on their, never totally deleted the db (just the tables) and just moved over all the tables and files from 2.2 to the new server. I assume it was the 2.1 install of the database on the new server that messed stuff up, so i fixed it by...

   1. Totally remove the db + user in cpanel (mysql databases)
   2. create a new table and user as usual, update the wp-config file to reflect (and these are all 2.2 files), including adding define('DB_CHARSET', 'utf8'); and define('DB_COLLATE', ''); to it.
   3. go through the normal install routine with the 2.2 files (wp-admin/install.php)
   4. once 2.2 has set up the db tables, drop them then import your tables from the other server.

   So far it all seems to work fine, and may have solved my old greymatter import problems too.

   Only weird thing is, after the 2.2 install, all tables showed as utf8_unicode_ci, and after the import they're now all latin1_swedish_ci again but without any problems.

Topic Closed

This topic has been closed to new replies.