[wp-trac] [WordPress Trac] #21767: Remove stripslashes from API functions

[WordPress Trac]

#21767: Remove stripslashes from API functions
-------------------------------------------------+-------------------------
 Reporter:  alexkingorg                          |       Owner:
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
Component:  General                              |  Review
 Severity:  normal                               |     Version:  trunk
 Keywords:  has-patch needs-testing needs-unit-  |  Resolution:
  tests                                          |
-------------------------------------------------+-------------------------

Comment (by nacin):

 I don't know how helpful it is to focus on particular solutions — whether
 its extra functions or parameters doesn't matter much. What matters most
 is plotting a broad course to saner ground. Very similarly related is
 #18322. Yes, this will be a major paradigm change, but it is absolutely
 necessary.

 We need to figure out what expected-slashed situations can safely be
 classified a "bug" (if core is doing it wrong, that's a good indication)
 versus a breaking-change. Possible example of the former:
 wp_insert_post(), given that unslashing can/should be moved to edit_post()
 and the like in admin/includes/post.php. Example of the latter: the
 metadata functions.

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