Look at your validation function (the one referenced by your register_setting call). Whatever it returns replaces the entire setting in the database. So if it’s not getting the setting and then altering it and returning the entire setting, you’ll lose the data that you didn’t have it return.
This issue is now resolved. I am posting the solution, in case someone else finds it useful. I have modified my callback for adding the checkbox list of categories so that the selected categories are saved in an array instead of separate options. It will make it much easier to find said special category and … Read more
I had the same issue as you did, but I found how to fix it in this tutorial: https://digwp.com/2016/05/wordpress-admin-notices/ Basically, I had my settings page outside of the Settings menu, so I had to explicitly add settings_errors() to my options page and they started working. 🙂 Hope that helps.
add_action( ‘admin_init’, ‘register_page_options’ ); function register_page_options() { if (false == get_option(‘aicp_settings_options’)) { add_option(‘aicp_settings_options’); } // Add Section for option fields add_settings_section( ‘aicp_section’, __( ‘….text here….’, ‘aicp’ ), ‘display_section’, ‘aicp_settings’ ); // id, title, display cb, page // Add Field for selecting countries for which you wanna ban ads add_settings_field( ‘aicp_country_list’, __( ‘Select the countries’, ‘aicp’ … Read more
If there is problem only with html markup you should check example from official jQuery UI site here: http://jqueryui.com/tabs/ It looks like yours, but for work you must check if your site include stuff like jquery and jquery ui script, jquery css is important too. After that you should have script with: $( “#tabs” ).tabs(); … Read more
No, it is not. Use esc_html__( ‘string’, ‘text_domain’ ) instead (two underscores). Translated strings are unknown input. Unknown input is per default malicious. You don’t know where the language file comes from. It doesn’t even have to be the one you provided, because the path can be filtered or changed with a symlink. Even if … Read more
I wrote a tutorial for Incorporating the Settings API in WordPress Themes. The only real difference for Plugins is that you’ll use add_settings_page() instead of add_theme_page(). The rest should pretty much be the same.
The option will be stored in the table $wp_prefix . “options” as an array. You can get the option with $myoptions = get_option(‘plugin_options’); try var_export( $myoptions ); to see that. There is also a hidden page in wp-admin/options.php where you can see all saved options.
WordPress will not do any data sanitization for you. It does do sanitization/validation of the default options. You have to pass in the third argument of register_setting and either role your own validation callback or or use one of the builtins. If your options is only going to contain a string, you could do something … Read more
What you need to do is build your own data validation function. Ozh wrote a great tutorial about this earlier, but here’s the gist of it … Assume your options array is called $my_options and it contains three fields, ‘text’, ‘age’, and ‘isauthorized’. You would still register it the same way: register_setting( ‘my_setting’, ‘my_options’, ‘my_validation_function’ … Read more