There's an API call System.utf8conversion which will change all your tables to MySQL/MariaDB's utf8mb4 format, i.e. full unicode with emoji support, rather than the incomplete utf8 implementation of old.

I ran this and it worked fine but then found that when I add a custom fieldset, that table is set to the old UTF8 charset.


It's still the case as of v5.30 that the incomplete UTF8 support is hard coded into the core code.

The solution for now seems to be to re-run the System.utf8conversion routine after any time you create a field/fieldset.

  • Note that there is a PR 18642 to fix this, thanks Seamus! – artfulrobot Sep 30 '20 at 15:18
  • That PR is merged, but not in 5.31 so assume it will make it to 5.32 – artfulrobot Oct 21 '20 at 8:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.