utf8
when utf8mb4
isn't supported.
Sometimes, `DB_CHARSET` will be set to `utf8mb4`, even if the current setup doesn't support `utf8mb4`. After [38442], this can cause significant character set failures, causing the connection to fall back to `latin1`. Instead of doing this, we now check that the connection supports `utf8mb4` before trying to use it, and fall back to `utf8` when we need to. Fixes #37982 for trunk. git-svn-id: https://develop.svn.wordpress.org/trunk@38580 602fd350-edb4-49c9-b593-d223f7449a82
Description
No description provided
Languages
PHP
76.7%
CSS
10.9%
JavaScript
9.2%
Modelica
2.4%
HTML
0.6%
Other
0.2%