I figured it out after a little work. To start, I ended up using a single callback: array($this, ‘txs_loop_callbacks’) using the same add_settings_field registration above. Then I altered the final argument in the field resgistration, making each unique to that specific field: array(‘field’ => ‘txs_opacity_’.$i). Then in the loop callback I stored each field’s HTML … Read more
If the options have “visual” impact on the website, consider using the customizer, it gives immediate visual feedback on what changing a value means. If the settings have no visual impact on the website, then maybe they don’t belong in the theme after all, but in a separate plugin. There are always edge cases, so … Read more
So do I still need to hook admin_init and call those register_setting() if I did add_option() before? Yes. You need. You may add add_option to set the default value. Another call to add_option will do nothing. However, the idea of register_setting() is more than just add_option(). Each setting has the context page such as (general, … Read more
The API handles the nonce for the form part because you’re using the settings_fields call, which outputs the *-options nonce, and you’re passing the data to the options.php file for saving, which checks that nonce for you before saving the settings. This part the Settings API does indeed do for you. However, your tab code … Read more
It looks like whatever the issue is has something to do with upgrading to 3.8 and Magic Fields V2 being up to date. I changed define(‘WP_CACHE’, true); to false, made sure WordPress was up to date, made sure Magic Fields V2 is up to date, no other plugins were active and there were no other … Read more
Does this work for you? Seems to work when I try it. function qd_settings_api_init() { add_settings_section( ‘qd_theme_setting_section’, ‘Theme Reading Settings’, ‘qd_theme_setting_section_callback_function’, ‘reading’ ); add_settings_field( ‘qd_news_page’, ‘News Page’, ‘qd_news_page_dropdown_cbf’, ‘reading’, ‘qd_theme_setting_section’ ); if (delete_transient(‘qd_flush_rules’)) flush_rewrite_rules(); // * Added register_setting( ‘reading’, ‘qd_news_page’, ‘qd_sanitize’ ); // * Changed } /* Added this function. */ function qd_sanitize($input) { set_transient(‘qd_flush_rules’); … Read more
You simply need to visit the Settings > Permalink page (you don’t have to do anything there) after saving the settings. If I had written the saving function myself, I could just call flush_rewrite_rules() Not quite. flush_rewrite_rules() would have to be called after the custom post type is ‘updated’ to reflect the changes, that is, … Read more
If you’re using Settings API, then you should use a sanitize callback: register_setting( $option_group, $option_name, $sanitize_callback ); The myth is that the $sanitize_callback actually is a filter for your options when it’s saved in the database. This is the place where you can do something with your custom code. This is the sample code: register_setting( … Read more
You have to call add_settings_section() first, pass a unique ID and assign it to the page (poor name) discussion: add_settings_section( ‘ads_id’, ‘Extra Settings’, ‘ads_description’, ‘discussion’ ); Then register a callback to save your field(s) … // Register a callback register_setting( ‘discussion’, ‘ads’, ‘trim’ ); … and then register one or more fields: // Register the … Read more
After digging in the setting API I found the answer. Method 1 was correct, but the notification should not be done by hooking to admin_notices, rather by the function add_settings_error add_action (‘pre_update_option_my_var’, function( $new_value, $old_value) { //Do my validation $valid = ( ‘correct_value’ == $new_value ); if ( !$valid ) { //This fixes the issue … Read more