With the dashboard nagging me to upgrade to WP 2.7, I decided that I might as well clear the UTF8 conversion issue first.
Doing it the hard way turned out to a bit of a disaster. It didn’t help that the WP Codex entry was not written for people like me in mind. Unlike the WP Codex entry on Backing Up, there were no screen captures to guide the lost. The instructions lacked the kind of detail needed for those who want to be spoon-fed. Jargon and terminology were left unexplained. Overall, it was assumed that readers were familiar with mySQL. I don’t know anything about mySQL - I did not even know the difference between a table and a column. orz
After I ran into some problems, I back-pedalled to square one. Thankfully my backup restored the Latin1 database without any glitches.
I then decided to take a risk with the plugin that Kabitzin used last year even though the plugin author only maintained it up to WP 2.2 and the relevant WP Forum threads have reported data corruption due to using the plugin.
So far it seems ok. The view in phpMyAdmin also showed that the collation has been changed to utf8_general_ci. I haven’t to do any F&R yet. I’m really grateful to Kabitzin for writing and updating that UTF8 entry. Thanks, you’re the best!!
After that, the WP 2.7 upgrade was also completely smoothly. For once, I was quite happy and eager to upgrade. Assuming the one-click upgrade tool works properly, it will make WP upgrades, with their irritating frequency, so much less of a chore for site owners. Though plugin and theme writers are probably still pulling their hair out.
.gif)
©2008 hontou ni sou omou?. All Rights Reserved.
.