[wp-hackers] Using the page_options field to create custom
wordpress at tekartist.org
Wed Sep 12 01:34:42 GMT 2007
And one more for the road.
It actually doesn't really... (although that depends on how secure
you wanna be).
sanitize_option() will only run stripslashes on custom options.
I'd probably make a note of that in the codex page.
On Sep 11, 2007, at 21:29, Stephane Daury wrote:
> Scratch that question, I looked it up in /wp-admin/options.php.
> It does.
> On Sep 11, 2007, at 20:27, Stephane Daury wrote:
>> Oh that is cool, thanks!
>> Off the top of your head, do you remember if that saving had
>> sanitazation too?
>> On Sep 11, 2007, at 19:46, Callum Macdonald wrote:
>>> I've just added an article to the codex about creating new
>>> options pages based on a technique I discovered a few days ago.
>>> I found that if you set the form action to options.php and create
>>> a hidden field called page_options with a comma separated list of
>>> the fields on the page that should be mapped to options,
>>> WordPress will handle all the saving / redirection /
>>> permissions / etc for you.
>>> If I've missed anything or there's any errors, please let me
>>> know. Any feedback would be most welcome.
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers