[wp-trac] Re: [WordPress Trac] #4647: Text in database should not be entity-encoded

[WordPress Trac]

#4647: Text in database should not be entity-encoded
--------------------------+-------------------------------------------------
 Reporter:  redsweater    |        Owner:  anonymous
     Type:  defect (bug)  |       Status:  closed   
 Priority:  normal        |    Milestone:           
Component:  General       |      Version:  2.2.1    
 Severity:  normal        |   Resolution:  wontfix  
 Keywords:  needs-patch   |  
--------------------------+-------------------------------------------------

Comment(by redsweater):

 What do you mean when you say it needs to address the upgrade of
 everything that gets changed? Do you mean a user's existing
 (inconsistently encoded) data?

 It seems to me that at least putting an end to the addition of
 inconsistent data to the database would be a valuable improvement.  If
 Joseph's patch addresses the problem so that new users would not be
 building inconsistency into their database, it seems useful.

 Is it normal policy of the WordPress team to close bugs as wontfix just
 because there is not currently an acceptable patch?  Or is there more to
 the story of "wontfix"ing this bug than is summarized in the comment
 above?

 Daniel

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