network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 9 months |
| seen | May 15 at 23:44 | |
| stats | profile views | 1 |
|
Aug 10 |
awarded | Analytical |
|
Aug 10 |
accepted | Use of check_admin_referer with theme options and options.php |
|
Aug 9 |
asked | Use of check_admin_referer with theme options and options.php |
|
Aug 7 |
awarded | Scholar |
|
Aug 7 |
accepted | Default Wordpress settings API data sanitization |
|
Aug 6 |
comment |
Default Wordpress settings API data sanitization Chris - you're right. I was being a little slow, and had entirely forgot that serialisation would do the same thing. I had avoided the escaping problem (or at least fallen for it then solved it). Thanks again for the help. |
|
Aug 6 |
awarded | Editor |
|
Aug 6 |
revised |
Default Wordpress settings API data sanitization Added extra detail in response to an answer |
|
Aug 6 |
comment |
Default Wordpress settings API data sanitization and also thanks for the explanation. Not long winded at all when it provides so much useful detail. |
|
Aug 6 |
comment |
Default Wordpress settings API data sanitization I guess I'm slightly confused then. I am registering all the settings in one go as an array, and passing them all to a single validation routine. This just checks that everything is right (i.e. reg exp checking that an email is an email etc). I am doing no sanitisation, or referencing any of the Wordpress sanitisation methods. However one option value contains a <script> tag, which when viewed in the database has been converted to HTML entities. I assumed Wordpress was doing this by default for any options stored in the database |
|
Aug 6 |
awarded | Student |
|
Aug 6 |
asked | Default Wordpress settings API data sanitization |
