Error update 4.7

[kalin]

During the update

We run the SQL query:

ALTER TABLE `ibf_core_message_topics` ADD COLUMN `mt_alert` BIGINT UNSIGNED NULL ;

And we get an error

ERROR 1366 (HY000): Incorrect string value: '\xED\xA0\xBD\xED\xB8\x89...' for column 'mt_title' at row 238578
 

[Marc Stridgen]

This would indicate your database is not currently using UTF8MB4 on your site. I would advise reverting to backup at this point, and then actioning items showing within the support area of your admin CP

[kalin]

No, sorry,

mysql> show create table ibf_core_message_topics\G; *********************** 1. row *********************** Table: ibf_core_message_topics Create Table: CREATE TABLE ibf_core_message_topics ( mt_id int NOT NULL AUTO_INCREMENT, mt_date int NOT NULL DEFAULT '0', mt_title varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', mt_hasattach smallint NOT NULL DEFAULT '0', mt_starter_id int NOT NULL DEFAULT '0', mt_start_time int NOT NULL DEFAULT '0', mt_last_post_time int NOT NULL DEFAULT '0', mt_to_count int NOT NULL DEFAULT '0', mt_to_member_id int NOT NULL DEFAULT '0', mt_replies int NOT NULL DEFAULT '0', mt_first_msg_id int NOT NULL DEFAULT '0', mt_is_draft int NOT NULL DEFAULT '0', mt_is_deleted int NOT NULL DEFAULT '0', mt_is_system int NOT NULL DEFAULT '0', PRIMARY KEY (mt_id), KEY mt_starter_id (mt_starter_id), KEY mt_date (mt_date), FULLTEXT KEY mt_title (mt_title) ) ENGINE=InnoDB AUTO_INCREMENT=301023 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci 1 row in set (0.00 sec)

[kalin]

We fixed it, turned it off strict mode

[Marc Stridgen]

I suspect its not actually set in your conf_global.php file there. Could you please confirm you have this line

 

'sql_utf8mb4' => true

[teraßyte]

You have also a wrong utf8mb3 value in that list for character_set_system.

[Jim M]

It would be advised when converting to UTF8mb4 to always use our conversion tool, as it does seem there were a few issues here.

[kalin]

1 hour ago, Marc Stridgen said:

I suspect its not actually set in your conf_global.php file there. Could you please confirm you have this line

 

'sql_utf8mb4' => true

It is already set when the conversion is done:

$INFO['sql_utf8mb4'] = true;

14 minutes ago, Jim M said:

It would be advised when converting to UTF8mb4 to always use our conversion tool, as it does seem there were a few issues here.

The conversion was done many years ago with your admin panel tool

[Marc Stridgen]

It is actually likely what Terabyte mentioned above could have been causing your issues too. Glad to see you got the upgrade through, but you should really sort that problem out also