Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator James Huff

    (@macmanx)

    Actually, if that is indeed what you did, all you did was replace the word “latin1” with “utf8” in the file, no different than replacing all occurrences of the word “red” with “green.” If you didn’t also use your text editor to change the character set of the database file, you actually did not change the character set.

    While that text editor method is quick on small databases, it’s actually impossible on larger sites, as the database export will often exceed the maximum file size of the text editor.

    The only way to effectively change the character set in all database sizes is to follow the guide as written.

    Thread Starter hlanggo

    (@hlanggo)

    Sorry for very delayed reply as this issue made me hot under the collar 1-2 months ago so I didn’t want to revisit it (nor wish to point that most WordPress sites do not have humongous databases nor maintained by IT staff with elite skill levels).

    Unfortunately, I had to convert another small (old) site.

    The instructions I followed:
    https://alexking.org/blog/2008/03/06/mysql-latin1-utf8-conversion
    https://dreamdare.org/tips-tricks/fixing-database-error-illegal-mix-of-collations-latin1_swedish_ciimplicit-and-utf8_general_cicoercible/

    1) phpmyadmin export
    2) notepad++ to search and replace
    3) drop all tables
    4) phpmyadmin import
    (as always, back-up, back-up, back-up)

    Screencap of previous and after – https://i.imgur.com/9H7clbN.png

    I didn’t need to change (overall) database character set as it was already utf8.

    As for the guide, it should at least (prominently) include a method for small databases.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Can someone please update the Coverting Database Charaset guide?’ is closed to new replies.