[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         |  Resolution:
 Keywords:                |
--------------------------+------------------------------

Comment (by ZaMoose):

 Replying to [comment:4 johnbillion]:
 > Yeah but I think we need to block interaction at this point to prevent
 the data loss (or data corruption) that you experienced. Clearly an edge
 case, but not a nice one.

 One weird thing to note: in certain scenarios, we were noticing that
 autosaves were capturing the content, while user-initiated explicit save
 ops were eating it. I haven't looked too closely into this, but that at
 least suggests to me that we may want to see how the AJAX stuff is
 interacting differently and attempt to catch this there, too. (That is, if
 we feel like it could lead to data loss somehow.)

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