The issue is not with your code. It is due to how WordPress works internally. This has been reported as bug in 2012 (almost 10 years ago at this point). You can see the bug report here: https://core.trac.wordpress.org/ticket/21989 The thing is that update_option is called, which when the option does not exist, will call add_option … Read more
Personally I’d do it the same way, since it seems to be the only point where you can examine user input and validate it. Also, heavily borrowing from code sample in this excellent article: function wpPartValidate_settings( $input ) { if ( check_admin_referer( ‘wpPart_nonce_field’, ‘wpPart_nonce_verify_adm’ ) ) { // Create our array for storing the validated … Read more
WordPress does not natively use Ajax submits with Settings API, so there isn’t really best practice for it. I remember scbFramework having such option, but it was removed. Essentially there is nothing inherently more insecure to such submit, you should treat form data as untrusted regardless of submit method and appropriately sanitize and validate it … Read more
First of all you need function to calculate lighter and darker colors. Once you have values in hex form a fast way is: convert hex to rgb conver rgb to hsl lighter and darker hsl (that is easy) revert lighter and darker colors from to hsl to hex (hsl > rgb > hex) Settings API … Read more
You are using add_settings_field wrong: the function sl_wp_create_user is being passed as $args (and you probably don’t need any args), and it should be the sanitize callback for register_settings. Make the input like: function sl_render_users_input() { echo ‘<input id=”num_users[value]” name=”num_users[value]” type=”input” value=”” />’; } And the sanitize function: function sl_wp_create_user( $input ) { if( isset( … Read more
This slide-out panel for picking a widget or nav menu item to add is specific to the implementations of Widgets and Nav Menus in the Customizer. There is no generic facility for adding this UI feature, so I suggest looking at Core to look at how it is implemented there to copy into your plugin. … Read more
Found it; One needs to use a so-called ‘whitelisted’ group: register_setting(“reading”, “honeycomb-reading-share”); Existing option-pages seem to all have a group-name that corrsponds to their page-name.
Why isn’t the following option getting saved? Because the database option name (the second parameter for register_setting()) is aa_myoption, hence the input name has to be aa_myoption or in the array notation like aa_myoption[my_field]: <input name=”aa_myoption”> <!– like this –> <input name=”aa_myoption[my_field]”> <!– or this –> Secondly, when you retrieve the option value and when … Read more
Is there a better, more efficient way – considered a “best practice” – to approach this? Yes! Storing structured data in a single option is bad practice. You should use the option name to seperate your data. Otherwise by using arrays and objects, WordPress cannot store those in the database, so it has to turn … Read more
For anyone else that may not have read the above comments and are having a possibly similar issue, @epilektric has answered the question stating that the = sign was missing after the value attribute under the field_1 and field_2 functions.