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

WordPress Trac noreply at wordpress.org
Tue May 19 16:16:59 UTC 2015


#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 chriscct7):

 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 searching on WP
 upgrades causing problems.
 Actually given how complex WordPress core is, they're relatively simple.
 The number of search results on Google isn't a good way to gauge "issues"
 as WordPress now powers 23% of all websites roughly. There will be issues
 even if there wasn't an upgrade routine, simply because of things out of
 WordPress's control (like hosting issues, etc).
 >
 > What is the process for doing a review on the upgrade architecture?  Is
 this discussion the primary control?

 This is a far more complicated matter than a simple characterset upgrade.
 The release also fixed a pair of security issues, and solved some long
 standing table schema issues. The schema updates were discussed at length
 for several years before they happened, along with many people testing the
 numerous alpha (trunk), and formal beta and rc releases. The best way to
 get involved with helping with this, if you'd like, is to help test beta
 and release candidates. They are announced on make.wordpress.org when they
 are available.

 In the future, you should test upgrades for plugins, themes and WordPress
 core using a test install. Sean Davis wrote a great guide on why and how
 here: https://easydigitaldownloads.com/blog/staging-site-e-commerce/

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


More information about the wp-trac mailing list