[wp-trac] [WordPress Trac] #32127: Broken support for utf8mb4 with the mysql extension

[WordPress Trac]

#32127: Broken support for utf8mb4 with the mysql extension
-------------------------------------+--------------------
 Reporter:  kovshenin                |       Owner:
     Type:  defect (bug)             |      Status:  new
 Priority:  high                     |   Milestone:  4.2.3
Component:  Database                 |     Version:  4.2.2
 Severity:  critical                 |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+--------------------

Comment (by BearlyDoug):

 Replying to [comment:17 ilovewpsomuch]:
 > This is so cool, how fumbling of a character set issue and little flaws
 in this hugely complicated upgrade engine, results in my company having to
 discontinue sales and me being not deal with the fallout.  If I had a vote
 I would vote for making the upgrade process short.  With such a long and
 intricate process, it is inevitable that breakdowns would be routine,
 which indeed they are, as shown Google searchng on WP upgrades causing
 problems.
 >
 > What is the process for doing a review on the upgrade architecture?  Is
 this discussion the primary control?

 If you do both of the patches I outlined in Comment 15, this will restore
 the functionality needed to add sites. Take care to note the location
 change for one of the patches (You might have to patch upgrade.php
 manually, completely).

 As additional character sets get added in, this might be an issue going
 forward... I'm not sure that the bug listed in this issue is entirely WP's
 fault.

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