I had to restore my database after a failed attempt at upgrading (a plugin I need hasn't upgraded yet.)
But now all umlauts and special characters in my blog are missing.
I assume this has something to do with the character encoding. When I imported the backup file into phpMyAdmin, I was asked for "Character set of the file." I used UTF. I assume this was wrong, but I don't just want to try again because I started replacing some of the characters by hand.
Did something go wrong with the original backup, or can I get all my special characters back by chosing the proper character set?
Open the backed-up sql file in a text editor, and look to see if the umlauts et al. are in there (you can do this by searching for part of a phrase that you know precedes an umlaut in one of your posts).
Also, the character encoding should be indicated for each table.
Thank you, filosofo. I checked the sql file in the built-in WinRAR viewer, and there seem to be some umlauts, but mainly they have been changed to something like this: Jürgen (I hope this displays right, as a combination of a wrong umlaut and a one-quarter sign.) Clearly, that's not what I'm looking for, but it looks like it retained slightly more info than the question marks I get on the site.
I'm not sure how to indicate encoding for each table.
The plugin doesn’t force any charset and uses the MySQL defaut one: latin1. So, in phpMyadmin, import your backup by selecting the latin1 charset.
This has nothing to do with blog entries charset in UTF-8, or other Tables settings.
I had to restore my database after a failed attempt at upgrading (a plugin I need hasn't upgraded yet.)
But now all umlauts and special characters in my blog are missing.
I assume this has something to do with the character encoding. When I imported the backup file into phpMyAdmin, I was asked for "Character set of the file." I used UTF. I assume this was wrong, but I don't just want to try again because I started replacing some of the characters by hand.
Did something go wrong with the original backup, or can I get all my special characters back by chosing the proper character set?
Thank you for your help.
Open the backed-up sql file in a text editor, and look to see if the umlauts et al. are in there (you can do this by searching for part of a phrase that you know precedes an umlaut in one of your posts).
Also, the character encoding should be indicated for each table.
Thank you, filosofo. I checked the sql file in the built-in WinRAR viewer, and there seem to be some umlauts, but mainly they have been changed to something like this: Jürgen (I hope this displays right, as a combination of a wrong umlaut and a one-quarter sign.) Clearly, that's not what I'm looking for, but it looks like it retained slightly more info than the question marks I get on the site.
I'm not sure how to indicate encoding for each table.
Thanks again for your help.
Don’t touch anything to your backup file !
The plugin doesn’t force any charset and uses the MySQL defaut one: latin1. So, in phpMyadmin, import your backup by selecting the latin1 charset.
This has nothing to do with blog entries charset in UTF-8, or other Tables settings.
RSS feed for this topic
Reply
You must log in to post.