Please excuse as some of this is a direct repeat of my reply in the thread "Upgrading from Legacy 2.0.11 to 2.8.x". Please note that I have searched this forum as best I can to find the answer to my question.
I am running two wordpresses. One was upgraded sometime ago from Legacy 2.0.11 to 2.7 (and recently upgraded to 2.8.4). The second wordpress, that I have just recently upgraded from 2.0.11 (which was stable and officially supported until very recently) to 2.8.4 was upgraded in one fell swoop going directly from 2.0.11 to 2.8.4 by following the steps in the codex. There appeared to be only a few glitches that were quickly ironed out by reading these forums and I thought I was back on track. Until I noticed several stray Âs in some of the older posts. And Ã»s instead of üs, Ã©s instead of és, Ã¢s instead of âs, etc. etc.
I looked in SQL and for the 1st wordpress, all the database tables have latin1_swedish_ci collation labels. In the most recently upgraded wordpress, I have two different character sets for the tables in the wordpress database: latin1_swedish_ci collation and utf-8
As a result of this giant glitch, I have stared at all of the codex "Converting Database Character Sets" at http://codex.wordpress.org/Converting_Database_Character_Sets
The very beginning gives me pause!
Warning: character set conversion is not a simple process.
And they're not just whistling Dixie. Alas, I'm stuck on the very first step:
Place notice that blog is out of service
How do I put the blog out of service? Is there some place in the wordpress dashboard that I can check to say "maintenance mode"? Or must I upload a special index page saying that it is unavailable?
In the thread entitled "Apostrophes and other special characters showing strange code after upgrade" noyz319 wrote the following:
In the codex it says:
Warning for those performing upgrades: If DB_CHARSET and DB_COLLATE do not exist in your wp-config.php file, DO NOT add either definition to your wp-config.php file unless you read and understand Converting Database Character Sets. Adding DB_CHARSET and DB_COLLATE to the wp-config.php file, for an existing blog, can cause problems — as Ryan Boren says, "your queries will go boom!"
I wish this info was included alongside the wordpress upgrade instructions. But is there a solution for people who have accidently done this? It seems to have done some sort of change/damage where just removing the lines of code are not providing a cure.
I see that there was a plugin created for this. Sadly, the utf-8-database-converter plugin is only compatible up to version 2.2
Does anyone have a babystep-by-babystep walkthrough for converting the database character sets? Thank you for any spoon-feeding you can supply.
EMorris etherwork.net/blog (2.8.4, WindowsXP, firefox3.0.14)