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

WordPress Trac wp-trac at lists.automattic.com
Mon May 11 14:03:24 GMT 2009


#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 Denis-de-Bernardy):

 Replying to [comment:8 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?

 yeah.

 > It seems to me that at least putting an end to the addition of
 inconsistent data to the database would be a valuable improvement.

 it could also introduce lots of issues if the data is not made consistent.

 > 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?

 understand it as wontfix until a patch that takes care of the upgrade is
 added, not wontfix ever.

 feel very free to re-open the ticket. I closed it because it would have
 stayed open for another two or three years pending the needed patch.

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


More information about the wp-trac mailing list