Gideon So Posted October 12, 2018 Posted October 12, 2018 I create a page reference field that allows user to create new page in the page edit page. I got this error: Error adding page "一二三" - SQLSTATE[HY000]: General error: 1267 Illegal mix of collations (ascii_general_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=' think it worked fine before I upgraded to 3.0.115. Any idea? Gideon
Gideon So Posted October 13, 2018 Author Posted October 13, 2018 Hi, I think this is a bug in the Page Reference field which was introduced after core version 3.0.106. I tested it with both multi-language and single language setting. Both of them give the same error when trying to create a page with non ASCII page name in the page edit page. Should I report this to the github bug issue? Gideon
Gideon So Posted October 13, 2018 Author Posted October 13, 2018 Hi, After testing with different version of the core. I found that the creation of page in page field function normally up to 3.0.110. It doesn't work anymore from 3.0.111. I will file a bug report to github. Gideon 1
Gideon So Posted October 19, 2018 Author Posted October 19, 2018 Please help to bump this issue in github. I think this bug is quite critical. https://github.com/processwire/processwire-issues/issues/724 Gideon 1
Gideon So Posted November 3, 2018 Author Posted November 3, 2018 This is a blocking bug that prevent non-ascii user upgrade the core beyond 3.0.110. @ryan any chance to take a look at it?? Gideon
BitPoet Posted November 5, 2018 Posted November 5, 2018 I've added a few details about the cause of the expection to the issue. In short, the pages.name table is created with an ascii charset by the installer, which should probably be changed. As a workaround, after installation, execute the following statement: ALTER TABLE pages MODIFY COLUMN `name` varchar(128) character set utf8 NOT NULL; (Change utf8 to utf8mb4 if you selected that character set in the installer) 1
Gideon So Posted November 6, 2018 Author Posted November 6, 2018 @szabesz I tested @BitPoet solution and it works well. Thanks BitPoet for the work around but hope that @ryan will make this change to the core. Gideon 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now