Duplicator Plugin Fails to Deploy New Package on Localhost

Hey @codeslayer2010,

There are a few items on the FAQ that may provide a solution with this issue, this one may get you going.

? ? – What is Compatibility mode & ‘Unknown collation’ errors?
? ? – https://snapcreek.com/duplicator/docs/faqs-tech/#faq-installer-110-q

If you don’t see any collation errors in the installer-log.txt file then you may be able to try the MySQL mode setting see:

? ? – What if I get database errors or general warnings on the install report?
? ? – https://snapcreek.com/duplicator/docs/faqs-tech/#faq-installer-260-q

Let me know if any of them help~

*** UPDATE (07/10/17) ***

Thanks for the quick reply Cory!

I love Duplicator and the work your team does to make it consistently
great!

SOLVED (Summary):

So, I tried your suggestions and I want to provide detailed feedback for posterity and to aid anyone else who may come across this post in search of assistance. But for those looking for a quick answer, The NO_ENGINE_SUBSTITUTION trick you mentioned worked for me.

QUICK QUESTIONS:

1. Can you shed any light in a “plain language”, but highly-granular way on what the problem likely was and why this trick fixed it?
2. Is there a setting in the backing-up phase of the Duplicator process that would eliminate having to do this workaround in the restoring phase?
3. What is collation in layman’s terms? When I worked in a phonebook factory as a youth, we put paper in a collator, which was a machine that vibrated large stacks of papers until all the pages were lined up along the ‘spine edge’. How does that relate to databases?

DETAILS:

I did a search for the word ‘collation’ in the installer-log.txt file. Not found. That told me that there must be no collation errors, so I moved on to your second suggestion.

The install Results had literally TONS of database write errors. Those errors all start similar to this:

**ERROR** database error write ‘Invalid default value for …

SOLUTION:

1. On the first page of the installer configuration (Step 1: Deploy Files & Database), click “Advanced Options”.
2. The second heading in this section says “MySQL”.
3. Set Mode to “Custom”. Now a new field that was previously hidden displays.
4. Type or paste this text into the new custom field, as shown in the screenshot:
   

   NO_ENGINE_SUBSTITUTION

5. Run the rest of the deployment steps as normal.

For me, this is what solved my issue of the database not copying, though I still don’t entirely understand why.

SUGGESTIONS & ERRATTA:

Instructions say:

‘On Step 2 of the installer under Advanced options locate the “MySQL Mode” setting’

Only problem is, that is actually on Step 1. Correcting this in the web text will help users and troubleshooters to avoid confusion and frustration, and come to a solution quicker.

• This reply was modified 7 years, 8 months ago by Eric Hepperle. Reason: added image
• This reply was modified 7 years, 8 months ago by Eric Hepperle.

Thanks for the feedback! You are correct the the NO_ENGINE_SUBSTITUTION setting will also work for invalid default date values, which is probably what you ran into…

In short if you create a package on a newer version of MySQL and then try install it on an older version that doesn’t properly handle certain language sets or settings from the newer version, then you can run into issues. The SQL Mode option can help in some of these scenarios. We hope in future versions to try and automatically handle this for users… If you want an overview of collation here is a good explanation.

https://stackoverflow.com/questions/341273/what-does-character-set-and-collation-mean-exactly

Cheers~