[wp-trac] [WordPress Trac] #24941: esc_sql in 3.6 changes how /r /n and maybe other characters handled

[WordPress Trac]

#24941: esc_sql in 3.6 changes how /r /n and maybe other characters handled
--------------------------+------------------------------
 Reporter:  sc0ttkclark   |       Owner:
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Formatting    |     Version:  3.6
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |
--------------------------+------------------------------
Changes (by sc0ttkclark):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 OK, going to close this as invalid, looks like we've got a lot of work to
 get Pods sanitization back under control for the 3.6 slashing changes.
 Some of this stuff just "worked" because it was legacy and it was the way
 it was, so it ended up spreading across the codebase. We were able to
 slash and unslash data willy nilly because esc_sql mapped to addslashes,
 but there's no quick fix for this because stripslashes_deep isn't a proper
 anti-mysql_real_escape_string in 3.6

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