Hi – I’ve been having an issue with automated incremental backups on my server using RunCloud. Based on their support, it looks like your plugin might have something to do with database collation (though I don’t fully comprehend this myself). I see there’s an option in advanced settings to do the following: Re-create the database tables of the plugin. Please note: this removes all settings and reviews. My question is how difficult is it to manually add back the reviews after this procedure?
The page I need help with: [log in to see the link]
It’s not complicated — the widget will simply reset to a fresh install state. You’ll just need to reconnect your account and configure the plugin again, the same way you did when you first installed it.
Could you please try to get an exact error message or a clear description from the support team about what they believe is not working correctly? Even an example of how they expect it to work would be very helpful. That way, we’ll have a concrete starting point to investigate further.
thx for reply. Here’s what the support team at Runcloud wrote:
It appears that the backup failed due to mydumper being unable to read the database collation for a table that has “utf8mb4_uca1400_ai_ci” collation. It looks like the root cause was that the CHARACTER_SET_NAME is NULL.
MariaDB [(none)]> SELECT * FROM INFORMATION_SCHEMA.COLLATIONS WHERE COLLATION_NAME LIKE '%uca1400_ai_ci%'; +----------------+--------------------+------+------------+-------------+---------+---------+ | COLLATION_NAME | CHARACTER_SET_NAME | ID | IS_DEFAULT | IS_COMPILED | SORTLEN | COMMENT | +----------------+--------------------+------+------------+-------------+---------+---------+ | uca1400_ai_ci | NULL | NULL | NULL | Yes | 8 | | +----------------+--------------------+------+------------+-------------+---------+---------+ 1 row in set (0.006 sec)
Kindly see the affected table for one of your databases ‘frazerfirm2_1736124192’
MariaDB [(none)]> SELECT TABLE_NAME, TABLE_COLLATION FROM information_schema.TABLES WHERE TABLE_SCHEMA = 'frazerfirm2_1736124192' AND TABLE_COLLATION = 'utf8mb4_uca1400_ai_ci'; +----------------------------+-----------------------+ | TABLE_NAME | TABLE_COLLATION | +----------------------------+-----------------------+ | wp_trustindex_google_views | utf8mb4_uca1400_ai_ci | +----------------------------+-----------------------+ 1 row in set (0.001 sec)
As a workaround, you need to change the collation manually from your end, by running the below command inside MySQL:
ALTER TABLE <tablename> COLLATE utf8mb4_general_ci;
So it seems like what they are saying is that your plugin is adding it’s data with the character set as ‘Null’
This issue is most likely not determined by our plugin, since no specific collation is set within it. As a solution, you can safely run the following SQL command in your database:
ALTER TABLE wp_trustindex_google_views COLLATE utf8mb4_general_ci;
Please check the collation directly on your database tables. In phpMyAdmin you can see it in the “Collation” column (screenshot attached: https://snipboard.io/tG43Xc.jpg).
When you run a collation change, MySQL may show “0 rows affected” even if the collation was actually updated. That message only refers to data rows, not to table definitions. The real way to confirm the change is to look at the “Collation” column in phpMyAdmin (see screenshot).
