Support

You may have to uncheck the “Allow UTE8MB4 auto-detection” option as one of your plugins seem to be incompatible with this feature which was added to WordPress in early 2017 (well over five years ago now).

Also check the “Use REPLACE instead of INSERT” option.

As per the documentation: ‘Use REPLACE instead of INSERT may be required if you keep getting MySQL errors about rows already existing in your tables.’

Did you check both the “Allow UTE8MB4 auto-detection” and the “Use REPLACE instead of INSERT” options?

No, you misunderstood me. I said ‘also check‘ meaning check that in addition to the previous one.

So, to clarify: please check both the “Allow UTE8MB4 auto-detection” and the “Use REPLACE instead of INSERT” options.

Can you please send me a link to download your backup archive? I will try to restore it locally to understand what is going on.

I have tried both links you sent me with Microsoft Edge and Google Chrome (fully updated) on Windows 11. Unfortunately, they both get stuck on "We're nearly ready..." with the Download button greyed out, not letting me download the file.

Can you please use a different file transfer service?

Thank you for this link, it worked for me.

So, I have good news and bad news for you.

The good news is that I was able to restore your site on Windows, Linux and macOS just fine, using the default options without changing any of the settings in the Restore Database page.

The bad news is that the most likely cause of your problem is that your local server is using an outdated version of MySQL (5.7 or earlier) whereas the server you backed up from is using a modern version of MySQL (8.0).

The best way to resolve this issue is updating your local server to a new version which includes a modern version of MySQL. Newer versions of MySQL do not have the 767 byte limit for all keys on the table which is what you are hitting.

The other alternative is to force ANGIE to downgrade all your UTF8MB4 (4-byte UTF-8) to UTF8 (3-byte UTF-8). The problem with that is that you might lose something, namely any four byte Unicode characters such as Emoji. This data will be unrecoverable, so if you later back up the local site and try to restore it on your server these characters will be lost forever. If you understand this and you are fine with it modify the default Database Restoration settings as follows:

- Use REPLACE instead of INSERT: check

- Force UTF-8 collation on tables: check

- Allow UTF8MB4 auto-detection: uncheck (clear)

This tells the restoration script to pretend that UTF8MB4 is not a thing and try to forcibly downgrade everything to the older, 3-byte UTF8 encoding. Also note that while this works in most cases, it may not work always. If you still get an error you have no alternative other than upgrading your local server environment.