mysql migration encoding fix – is this safe?

  • DaveMcK

    (@davemck)


    16 years ago

    Lots of trouble migrating to a new host – particularly with moving the database. Lots of gremlins appear in the imported version (borked apostrophes, quotes etc), all to do with utf-8 reading Latin1 entries. There appear to be some complex solutions to do with configuring the dumps/imports correctly, but the easy thing that works seems to be to edit the wp-config.php file and change

    define(‘DB_CHARSET’, ‘utf8’);
    to
    define(‘DB_CHARSET’, ‘latin1’);

    It definitely works – but could it cause problems? If so, what of problems?

    Thanks in advance.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter DaveMcK

    (@davemck)

    So it’s perfectly alright to do this?

    We’re having a similar situation: it’s inconvenient to convert the database to utf8 because of the way we have it set up, and it’s much easier to just change the charset in wp-config.php to latin1 instead.

    Is this safe to do?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘mysql migration encoding fix – is this safe?’ is closed to new replies.