Discussion in 'General' started by illuder, Mar 12, 2020.

  1. illuder

    illuder Member HowtoForge Supporter


    Whenever I upload an SQL file via phpmyadmin for wordpress , i get the message below. I've seen various solutions online, but I'm asking if there's a permanent solution to resolve this, perhaps a setting? or an upgrade of the software or bug fix? Whatever to remove the inconvenience..

    CREATE TABLE `wp_commentmeta` (
    meta_idbigint(20unsigned NOT NULL AUTO_INCREMENT,
    comment_idbigint(20unsigned NOT NULL DEFAULT '0',
    meta_keyvarchar(255COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
    meta_valuelongtext COLLATE utf8mb4_unicode_520_ci,
    PRIMARY KEY (`meta_id`),
    KEY `comment_id` (`comment_id`),
    KEY `meta_key` (`meta_key`(191))
    ENGINE=MyISAM AUTO_INCREMENT=41 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
    MySQL saidDocumentation

    #1273 - Unknown collation: 'utf8mb4_unicode_520_ci'
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Reject MySQL and mariadb versions should support that collation out of the box as far as I know. Do you use a old MySQL or MariaDB version or an old operating system in general?
  3. illuder

    illuder Member HowtoForge Supporter

    I'm using MariaDB with the latest CentOS,

    however, I've come across this awesome plugin which is making moving my wordpress sites from cpanel onto ISPconfig3 seamless and very quick. It fixed the collation issue by using legacy.

    If anyone is moving wordpress full sites, I strongly recommend you look into this plugin:

Share This Page