Support » Plugin: Duplicator - WordPress Migration Plugin » Possible replace utf8mb4_unicode_520_ci before package cerated?

  • Resolved Jonas Lundman

    (@intervik)


    Since WP 4.6, they forcing utf8mb4_unicode_520_ci, when possible, (no matter WP CONFIG). When using this plugin and migrating from our local development installs, many servers does not support “utf8mb4_unicode_520_ci”.

    After using Duplicator for ages, since 4.6 this becomes a pain in the ass, manually unpack the Duplicator files and search and replace, etc etc…

    Is it possible to do the replacement inside the package (files in the archive) to replace “utf8mb4_unicode_520_ci” with for ex “utf8mb4_general_ci”, when the package is created?

    If not, any smart trix to force WP use the same coll as decided in WP_CONFIG?

    / Thanks for a great work all those years.

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

    (@corylamleorg)

    Hey @intervik,

    Have you tried Installer > Step 2 > Options > “Apply legacy collation fallback support for unknown collations types” checkbox by chance?

    There is also another option when you build the package on step1 > Archive > Database Tab > Compatibility Mode > mysql40

    I would try the installer one first.

    Let me know if this helps…

    Thxs~

    Hi, and thanks for your time!

    Well, we tried those things.

    First “Before doing package” Database Tab:
    Compatibility Mode
    This option is only available with mysqldump mode.

    Even if we switch to dump mode, the coll cant be set here, only msql and we dont wanna change that as the version is not a problem for the live servers. (Using Duplicator in dump mode also is buggy, gets interupted and stops most of the time, php doesnt)

    Second: Step 2 “Apply legacy collation fallback support for unknown collations types” is only available after the zip has been unpacked, not on pre-test database connection link. And we dont wanna unpack before we got the database test ok (mostly for client given us correct database connection information – we don wanna give away a install if we cant deploy it)

    And even so, if we unpack and use the checkbox, the script as we can see, fails, maybe bec its trying to step backwards from unicode_520_ci directly to utf8_general_ci, not “utf8mb4_general_ci”, as the live server uses.

    So its only works if we search and replace in “dup-installer” as mentioned in question (and in all files, only .sql file not enough, there must be in all 81 hits in 4 files).

    CONCLUSION:
    We need a solution -as the question- where Dublicator not “Packing”/ creates the package, with “utf8mb4_unicode_520_ci”. Instead using the one in WP_CONFIG (in our case: “utf8mb4_general_ci”)

    As WordPress ignores WP_CONFIG, I asume Duplicator do that as well. There must be some way to override that? / Or filter in the coll to use?

    Thanks for any tips on this…

    Plugin Author Cory Lamle

    (@corylamleorg)

    Hey @intervik,

    Thanks for the detailed feedback. I have logged this as a task for us to look into. It may be a few versions out, but it is in our backlog of items to research.

    Again thanks for helping to improve the product!

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