WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Charter display after 3.2.1 migration (5 posts)

  1. guyshomenet
    Member
    Posted 2 years ago #

    After long delays, I updated from 2.8.6 to 3.2.1.

    After updating (which I have since rolled-back) various characters are displayed incorrectly. Apostrophes and hyphens are displayed as a diamond with a question mark inside (see URL below for a screen grab of the 3.2.1 version).

    There was a MySQL 4.x to 5.x migration, but via phpmyadmin I can browse to the same rows for the most recent posts and see that the data are plain apostrophes and hyphens. Thus I doubt I have a MySQL migration issue (database was dumped using mysqldump and both with/without --default-character-set=utf8, imported into a new 5.0 database using phpmyadmin, same results).

    http://www.GuySmith.org/pme/blog-snap.png

  2. esmi
    Theme Diva & Forum Moderator
    Posted 2 years ago #

    I think the problems may have occurred because you tried to carry out a pretty big upgrade in a single step instead of multiple smaller steps:
    2.8.6 -> 2.9 -> 3.0 -> 3.2.1

    Did you remember to backup your database before you began?

  3. guyshomenet
    Member
    Posted 2 years ago #

    @esmi: Yes, everything was backed-up and returned to its original condition (always, always, always).

    I don't see how the leap from 2.8.6 to 3.2.1 would be the source of the problem. Assuming I'm correct about the MySQL issues, then it appears to be the way WP processes and displays the data extracted from MySQL. That should be an identifiable/correctable config/bug.

  4. esmi
    Theme Diva & Forum Moderator
    Posted 2 years ago #

    There are no known issues of this kind amongst millions of other users, so this must be specific to your site.

  5. guyshomenet
    Member
    Posted 2 years ago #

    Thanks to esmi for replies as useless as a politician's promise.

    After a fair bit of web scanning, the problem was identified as the MySQL 4.x to 5.x character set conversion hell. There are a few solutions offered around the web, but the best (and the one that actually worked given the added problems 1and1 creates) was found at:

    http://www.bluebox.net/news/2009/07/mysql_encoding

    Good luck to everyone else in similar migrations.

Topic Closed

This topic has been closed to new replies.

About this Topic