[wp-trac] [WordPress Trac] #32051: Creating new posts/terms with non-English characters is broken for tables with cp1251 collation in 4.1.2

[WordPress Trac]

#32051: Creating new posts/terms with non-English characters is broken for tables
with cp1251 collation in 4.1.2
--------------------------+-----------------------
 Reporter:  vloo          |       Owner:  pento
     Type:  defect (bug)  |      Status:  accepted
 Priority:  high          |   Milestone:  4.2
Component:  Database      |     Version:  4.1.2
 Severity:  critical      |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------

Comment (by vloo):

 I guess @LewisCowles is right that we shouldn't keep supporting all kinds
 of weird legacy collations in the long run. Still this is a mess that
 WordPress did or let people do to themselves "long time ago, in a galaxy
 far, far away, where people are not English speaking". Best solution would
 be to have a "band-aid" until there is a database migration script that
 converts people's databases to utf8mb4.

 Either this, or a screaming warning notification at the upgrade screen,
 telling the administrator that their site will be in trouble because of
 their collation, that is being left unsupported in the next major release.

 Support over legacy technology should never be dropped silently during a
 security release, letting people save themselves (if they can) after they
 find out their sites are actually safe but not functioning properly.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/32051#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform