We put in a couple notes, an alternative example and a couple warnings
("please note"s), but didn't remove the originals (just clarified the
situations where they'd be bad.On Tue, Sep 25, 2012 at 12:45 PM, Lorelle on WordPress <[email protected]> wrote: > Thanks for pointing this out. Let us know when they have made changes and > we'll get one of ours to take a look. > > Thanks! > > Lorelle > > > On Mon, Sep 24, 2012 at 10:21 AM, Ken (WraithKenny) > <[email protected]> wrote: >> >> A senior coder here is going to edit it. Feel free to review his >> changes and/or discuss on this thread, I'll forward it on :) >> >> On Mon, Sep 24, 2012 at 1:18 PM, Ken (WraithKenny) >> <[email protected]> wrote: >> > Hi everyone, >> > >> > The codex page here >> > http://codex.wordpress.org/Function_Reference/stripslashes_deep that >> > to my eyes gives terrible advice. I consider myself to be ann >> > "intermediate" level coder, so I'd like some feedback before making >> > edits here. First, the example recommends get_magic_quotes_gpc() but I >> > understand this to be unreliable, especially in a WordPress >> > environment (WordPress emulates and "turns on" magic quotes >> > regardless), and second, it gives example code $_POST = >> > stripslashes_deep( $_POST ); which seems like it'd be especially bad >> > practice... or am I wrong? >> > >> > Thanks, >> > Ken >> _______________________________________________ >> wp-docs mailing list >> [email protected] >> http://lists.automattic.com/mailman/listinfo/wp-docs > > > > _______________________________________________ > wp-docs mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-docs > _______________________________________________ wp-docs mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-docs
