Support » Plugin: Duplicator - WordPress Migration Plugin » utf8mb4_0900_ai_ci, MySQL 8.0 => MariaDB 10.3.27

  • Resolved onico0



    utf8mb4 has become the default character set, with utf8mb4_0900_ai_ci as the default collation in MySQL 8.0.1 and later ?

    Today, I had to migrate a website from a remote web server running MySQL 8.0.2x to my own CloudLinux/cPanel server running MariaDB 10.3.27.

    I got the infamous error :

    Check Collation Capability Fail
    utf8mb4_unicode_520_ci: Pass
    utf8mb4_0900_ai_ci: FAIL
    utf8mb4_general_ci: Pass
    utf8_general_ci: Pass

    I tried to fix it fast and I googled the error, found the forum and see your team always link to the your FAQ that say :

    UTF8MB4 FORMAT: If the current MySQL server version detected is below 5.5.3 (release on April 8th 2010) then support for utf8mb4 tables will not work. The utf8mb4 format is only supported in MySQL server 5.5.3+. It is highly recommended to upgrade your version of MySQL server on this server to be more compatible with recent releases of WordPress and avoid issues with install errors.

    But, no way to update our latest stable version of MariaDB 10.3 (on CloudLinux server) to MySQL 8.0.x.

    Also, Legacy checkbox, Compatibility mode doesn’t help for me (?)

    Exporting DB by PhpMyAdmin with MYSQL4 compatibility did not work.

    So, my solution was to manually edit each table structure, and each fields concerned by the utf8mb4_0900_ai_ci collation, all through PhpMyAdmin, in the previous server.

    I replaced everything by utf8_unicode_ci instead
    (I hope it doesn’t broke anything, it seems ok).

    On the database in PhpMyAdmin > Operations > Collation, it seems we can bulk editing Collations “Change all tables & columns collations” but I am not sure it is safe to do that or not as I want keep collations for other tables not settled to utf8mb4_0900_ai_ci.

    Anyway… all that report to suggest to the Duplicator Team considering implementing “collation conversion” in Duplicator (if technical possible?? a very big deal??), as I think, this issue will happen often, is not it ?

    Thanks for your work!

Viewing 1 replies (of 1 total)
  • Plugin Author Cory Lamle


    Hey @onico0,

    Some of those changes have been propagated into the PRO product but are still rather new, I’m not 100% sure if they would solve your exact problem. They will probably bubble down into the free version over the next year or so. Since free has such a large user base we needed to get better feedback from the PRO customers before pushing them down…

    In the meantime your welcome to submit a support ticket for a trial version to see if it solves your solution Please provide a link to this forum thread when submitting the ticket.


Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.