[wp-trac] [WordPress Trac] #25693: blog_charset should be checked for null values

[WordPress Trac]

#25693: blog_charset should be checked for null values
--------------------------+-----------------------------
 Reporter:  ZaMoose       |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Charset       |    Version:  trunk
 Severity:  major         |   Keywords:
--------------------------+-----------------------------
 We've encountered an error wherein a blog in a multisite network's
 `blog_charset` was nuked. This led to posts entered from the editor
 (visual and text) having random bits eaten. This was particularly
 pronounced when using text copied from Word documents.  This is related to
 #23688, I think.

 It seems as though PHP 5.4 makes some weird assumptions when you have a
 blank/null charset.  Suggest we check for null values and fall back to,
 say, UTF-8 if none is found.

 @grantlandram, @dkotter and I found this one under duress.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/25693>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software