-
Suggestion
-
Resolution: Done
-
None
-
100
-
2
-
As a confluence Administrator, when I set up a new instance of confluence 6.4 with MySQL using the utf8mb4 character set, the installer will refuse to continue with the datasource. This should be reverted to the behavior from 6.3 where it's possible to use this encoding for a new install.I can live with the somewhat nonsensical warning about unsupported character set / collation.
Currently, I would need to first install version 6.3, go through the Setup Assistant, then upgrade to 6.4.
INFO: UTF8MB4 is now supported in confluence 7.3.1. Please see the notes to migrate from UTF8 to UTF8MB4 here.
If you are unable to migrate to UFT8MB4 please read
CONFSERVER-18509 - Confluence should handle this gracefully for most scenarios where 4-byte characters are used by providing meaningful error messages.
- blocks
-
CONFSERVER-34420 Update Confluence to support Emoji characters
-
- Closed
-
- is related to
-
CONFSERVER-18509 MySQL databases incapable of handling 4byte UTF-8 Characters. Confluence should handle this gracefully
-
- Closed
-
-
CONFSERVER-59375 Updating ATST Troubleshooting and Support Tools breaks MySQL health checks
-
- Closed
-
A fix for this issue is available to Server and Data Center customers in Confluence 7.3.1
Upgrade now or check out the Release Notes to see what other issues are resolved.