Support » Plugin: amr users » TABLE `wp_amr_reportcache`

  • Anna-marie hi,

    amr users 4.3
    MySQL 5.6.32-78.1
    phpMyAdmin 4.3.8
    PHP:5.6.29

    Have encountered a strange anomaly in exporting/importing my wordpress mysql database in phpmyadmin.(migrating servers)

    phpmyadmin does not like your wp_amr_reportcache table. It references an incompatible collation type of ‘utf8mb4_unicode_520_ci’

    All other WP tables are utf8mb4_unicode_ci

    Any suggestions? Did want to manually change (break?) anything prior to consulting with you. Have read quite a bit in various forums. Modifying phpmyadmin export/import parameters has not worked for me.

    See error message below –

    thanks – GARRY

    CREATE TABLE wp_amr_reportcachelogging (
    id bigint(20) NOT NULL AUTO_INCREMENT,
    eventtime datetime NOT NULL,
    eventdescription text COLLATE utf8mb4_unicode_520_ci NOT NULL,
    PRIMARY KEY (id)
    ) ENGINE=MyISAM AUTO_INCREMENT=18 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
    MySQL said: Documentation
    #1273 – Unknown collation: ‘utf8mb4_unicode_520_ci’

Viewing 3 replies - 1 through 3 (of 3 total)
  • oops – it actually this table as you will see in error message:

    wp_amr_reportcachelogging

    update:

    — manually changing wp_amr_reportcachelogging and wp_amr_reportcachelogging->eventdescription to utf8mb4_unicode_ci in phpMyAdmin, does solve my WP data export/import problem, but yet to test if this has any effect on app functionality.

    GARRY

    Plugin Author anmari

    (@anmari)

    Hi Garry,

    all those utf8mb4… collations are coming from your system.

    The Plugin references the wp global $charset_collate and if it is empty, it sets a default for the sql statement ‘ DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci ‘

    So whatever was going on there, the collation was set by your sites environment. Hope it works for you now.

    Aside:
    Since wp 3.5 there is now a function $wpdb->get_charset_collate(), which I will update the plugin to use next version. (Thanks for flagging)

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