#3026 closed defect (bug) (fixed)
Converter table does not limit max index lengths of key
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | 2.5.12 | Priority: | high |
Severity: | major | Version: | 2.4 |
Component: | API - Importers | Keywords: | has-patch |
Cc: |
Description
From https://bbpress.org/forums/topic/smf-to-bbpress-error-utf8mb4/#post-179480.
Since WordPress 4.4, utf8mb4
is the recommended character set and utf8mb4_unicode_ci
is the recommended collation. This combination reduces the size of the indexable length down to 191 characters, and the converter table tries to create keys that are 255 characters long.
This will result in the following error:
WordPress database error: [Specified key was too long; max key length is 1000 bytes] CREATE TABLE wp_bbp_converter_translator ( meta_id mediumint(8) unsigned not null auto_increment, value_type varchar(25) null, value_id bigint(20) unsigned not null default ‘0’, meta_key varchar(255) null, meta_value varchar(255) null, PRIMARY KEY (meta_id), KEY value_id (value_id), KEY meta_join (meta_key, meta_value) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci
This is a pretty major deal IMO, since anyone trying to convert on any modern WordPress installation will have issues. Recommend we back-port the fix to the 2.5 branch for 2.5.12.
Attachments (1)
Change History (5)
Note: See
TracTickets for help on using
tickets.
Limit maximum index length to 191