#1273 – Unknown collation: ‘utf8mb4_unicode_520_ci’

I have a WordPress website on my local WAMP server. But when I upload its database to live server, I get error

#1273 – Unknown collation: ‘utf8mb4_unicode_520_ci’

Any help would be appreciated!

Solutions

You can solve this by finding

ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

in your .sql file, and swapping it with

ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci;

I believe this error is caused because the local server and live server are running different versions of MySQL. To solve this:

  1. Open the sql file in your text editor
  2. Find and replace all utf8mb4_unicode_520_ci with utf8mb4_unicode_ci
  3. Save and upload to a fresh mySql db

Hope that helpsenter image description here

In my case it turns out my
new server was running MySQL 5.5,
old server was running MySQL 5.6.
So I got this error when trying to import the .sql file I'd exported from my old server.

MySQL 5.5 does not support utf8mb4_unicode_520_ci, but
MySQL 5.6 does.

Updating to MySQL 5.6 on the new server solved collation the error !

If you want to retain MySQL 5.5, you can:
- make a copy of your exported .sql file
- replace instances of utf8mb4unicode520_ci and utf8mb4_unicode_520_ci
...with utf8mb4_unicode_ci
- import your updated .sql file.

Tags: Mysql / SQL / Wordpress

Similar questions

Ionic 3 Push Notification Error "statusText":"Unknown Error","name":"HttpErrorResponse","message":"Http failure response for (unknown url)
I'm using Ionic 3 with a backend on Wordpress 4.9.8 and I'm follow the guide to make the push notification: https://www.delitestudio.com/it/wordpress/push-notifications-for-wordpress/documentation/#configurePushNotificationsForWordPress I'm at point 4.1 and I wrote this: but on post response I get the error: and this warnings:
problem with Mysql Unknown error starting mysql and Unknown error starting apache
I have problem with all version of bitnami. When I shut down or restart my pc, WAMP can't connect with MySQL. I closed skype but still have the same problem. I also changed to XAMPP but the problem still there when I shut down. In the end, I revert to bitnami and I still have the same problem. I've watched all the troubleshooting video and do somet...
Default table collation on plugin activation?
I'm following this to make my plugin auto-create a table when the plugin is activated, but what happens is that while all the tables (the whole db) are utf8_general_ci, the newly created table is latin1_swedish_ci... Why isn't it also utf8? I thought it would also be utf8 by default since I have: in my wp-config.php... I have everything exactly the...
What is the correct way for plugins to create tables with special charset/collation considerations?
I'm using WordPress >=3.8. The default charset/collation values in wp-config.php are I am in a situation where utf8_general_ci would be adequate, but something more specific (utf8_danish_ci) will always be able to describe my data better. It is also the case that the data, which is fetched from an external source, will always be UTF-8. I am develop...
database collation differences
I have a database for a site I am developing in WAMP. The collation for the database is latin1_swedish_ci but every table in the database is utf84mb_unicode_ci. Should I be worried about this? In the future I can use utf84mb_unicode_ci for both, but what about the databases I already have content in?
Please explain how Wordpress works with MySQL character set and collation at a low level
As the question title suggests, I'm looking to understand how Wordpress works with MySQL character sets and collation options. As I will show below, things don't make much sense to me... I installed Wordpress by following the instructions on their installation page: https://codex.wordpress.org/Installing_WordPress As part of the instructions, I fol...

Also ask

We use cookies to deliver the best possible experience on our website. By continuing to use this site, accepting or closing this box, you consent to our use of cookies. To learn more, visit our privacy policy.