[wp-trac] [WordPress Trac] #21767: Remove stripslashes from API functions
WordPress Trac
noreply at wordpress.org
Thu Feb 28 16:13:56 UTC 2013
#21767: Remove stripslashes from API functions
-------------------------------------------------+-------------------------
Reporter: alexkingorg | Owner:
Type: task (blessed) | Status: new
Priority: normal | Milestone: 3.6
Component: Formatting | Version: 3.4
Severity: normal | Resolution:
Keywords: has-patch needs-testing needs-unit- |
tests 3.6-early |
-------------------------------------------------+-------------------------
Comment (by alexkingorg):
We knew there would be a small number of folks who were "doing it right"
that would have to update their themes/plugins accordingly. I have several
plugins I would need to change now as well. In discussing this with Nacin
at WCSF, he put it this way "yes, but you'll update your plugins". I think
he's right - people that knew enough to do it "right" by slashing stuff
are pretty likely to update their code accordingly.
The mass benefit to the change was to "fix" the majority of usage which is
incorrect. In talking with other WP devs about this issue at a number of
WordCamps over the last year, I am pretty confident that most custom site
build usage of wp_insert|update_post() is currently incorrect. Adding
another parameter misses that mark.
I don't have the plugin repo checked out anymore (and won't be on a fast
connection to do so for a week or so), but if someone could do a search
for wp_insert|update_post through the full repo, it might give us a better
sense of "general" usage. I do think much of the problem is a somewhat
"hidden" failure though, as much of the usage I've discussed with people
is in custom sites/implementations.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/21767#comment:95>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list