You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The module breaks Silverstripe 4+ site if you are using utf8mb4 unicode which requires full 4 bytes.
Although not tested (I simply removed this module and can have a look later), I guess the issue is caused by
The reason why it is a bug because Silverstripe itself supports full 4 bytes, and ideally the module would at least support the same requirements. SiteTree also uses Varchar(255) for URLSegment but that is fine.
Errors:
Couldn't run query:\n\nALTER TABLE \"RedirectedURL\" CHANGE \"ClassName\" \"ClassName\" enum('SilverStripe\\\\RedirectedURLs\\\\Model\\\\RedirectedURL') character set utf8mb4 collate utf8mb4_unicode_ci default 'SilverStripe\\\\RedirectedURLs\\\\Model\\\\RedirectedURL',\nCHANGE \"FromBase\" \"FromBase\" varchar(255) character set utf8mb4 collate utf8mb4_unicode_ci,\nCHANGE \"FromQuerystring\" \"FromQuerystring\" varchar(255) character set utf8mb4 collate utf8mb4_unicode_ci,\nCHANGE \"To\" \"To\" varchar(255) character set utf8mb4 collate utf8mb4_unicode_ci\n\n42000-1071: Specified key was too long; max key length is 767 bytes at ...\\vendor\\silverstripe\\framework\\src\\ORM\\Connect\\DBConnector.php:64)"} []
To replicate the issue, place this in your app.yml or mysite.yml and run dev build
The module breaks Silverstripe 4+ site if you are using utf8mb4 unicode which requires full 4 bytes.
Although not tested (I simply removed this module and can have a look later), I guess the issue is caused by
as it uses combined indexing.
The reason why it is a bug because Silverstripe itself supports full 4 bytes, and ideally the module would at least support the same requirements. SiteTree also uses Varchar(255) for URLSegment but that is fine.
Errors:
To replicate the issue, place this in your app.yml or mysite.yml and run dev build
The text was updated successfully, but these errors were encountered: