Serious issue with character encoding for SCTR database tables

  • Resolved rkhudoyberdiev

    (@rkhudoyberdiev)


    8 years, 3 months ago

    Dear StCR author,

    I was having problems with timeouts from Cloudflare recently, so I started digging deeper.

    I found out that the issue was with comment timeouts because I was getting illegal mix of collations error in my databases.

    Looking though the databases, I realized that wp_subscribe_reloaded_subscribers table was using utf8mb4 charset with utf8mb4_unicode_520_ci collation which was conflicting with default WordPress utf8 utf8_general_ci.

    Is there any fast fix by editing your plugin files or changing the database collation manually is the only option?

    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)

  • I got this issue on a new installation.

    To any who still need more instructions on how to fix:

    1. Backup your database.
    2. Confirm your backup is good.
    3. Open database in phpMyAdmin and click on the wpXXX_subscribe_reloaded_subscribers database table.
    4. Click on Structure Tab. Notice that the “subscriber_email” and “subscriber_unique_id” columns both have a Collation of: “utf8mb4_unicode_520_ci”, which needs to be changed to: “utf8mb4_unicode_ci”.
    5. Chick on the “Change” icon for each column and use the dropdown menu to change: “utf8mb4_unicode_520_ci” to: “utf8mb4_unicode_ci” and click “Save”.
    6. Test to see if that worked–it did for me. If not, restore your database from your backup.

    Thanks to the Developer for this great plugin and thelawstudentswife for reporting this bug and the solution on the GitHub support page.

    Thread Starter rkhudoyberdiev

    (@rkhudoyberdiev)

    Thanks for the reply. I did almost exactly the same except changed to utf8_general_ci and I guess it worked. There are no more cloudflare issues, nevertheless sometimes there are lags with comments resulting in double submissions. So yeah the solution works.

    Hi guys! Great to hear that you found a solve the issue. Just FYI The plugin does not control the collation in your database, so when this new table is created it takes the database default collation. I will take a deep look at it anyways.

    Regards.!!!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Serious issue with character encoding for SCTR database tables’ is closed to new replies.