While you are using Settins API, that’s why you don’t need to use update_option or add_option functions. Settings API would handle that by self. There were few issues that’s why your code is not working. 1. add_settings_section( ‘wpa_ad_insert_main’, ‘Ad Insertion Settings’, ‘wpa_ad_insert_section_text’, ‘wpa_ad_insert’ ); 3rd parameter is the callback function. Since, you don’t need this … Read more
You are using a code a bit dirty: foreach is not needed here, and I think you forgot to print the header color (see comment in following code). After that, if you want to print nothing if you have no customiztion, create an out variable and it’s not blank print the styles: add_action(‘wp_head’, ‘dynamic_options’); function … Read more
I’ve just run across this same issue myself on a project I am currently working on. Basically, what I did was break my settings into groups so they can then be displayed as a separate section(s): <?php class MyPluginSettings { /** * Constructor. * * @return void * @access public */ public function __construct() { … Read more
This is just a typo Wrong //wvdh-startpoint add_submenu_page( ‘wvdh-startpoint’, ‘page-from-plugin’, ‘menu-from-plugin’, ‘manage_options’, ‘plugin-slug’, ‘wvdh_settings_page’ ); Correct //wdvh-startpoint add_submenu_page( ‘wdvh-startpoint’, ‘page-from-plugin’, ‘menu-from-plugin’, ‘manage_options’, ‘plugin-slug’, ‘wvdh_settings_page’ );
If you check the checkbox and save the plugin options it will add option to the {prefix}_options table in the database. To make a checkbox checked you need to update_option(‘option_id’, ‘value’ ) for that checkbox on plugin activation. to do that you need to register plugin activation hook. Place the below code in the main … Read more
You can hide it using jQuery which will be inserted in the wp-admin header: add_action( ‘admin_head’, ‘wpse_239421_hide_section’ ); function wpse_239421_hide_section() { ?> <script type=”text/javascript”> jQuery(document).ready(function($) { $(‘[scope=row]’).closest(‘tr’).hide(); } ); </script> <?php } This will remove the closet tr bases on the scope=row.
https://make.wordpress.org/core/2016/10/26/registering-your-settings-in-wordpress-4-7/ The register_setting() function signature changed in v4.7 allowing an array for the third option in place of a callback function in prior versions. Passing an array to register_setting() in WordPress v4.6.x and earlier will result in the errors above. WordPress v4.6.8 function definition: https://github.com/WordPress/WordPress/blob/1aa173010736085a921beb10fd420d6d863419a5/wp-admin/includes/plugin.php#L1767-L1795 /** * Register a setting and its sanitization callback * … Read more
You could use the after_theme_switch hook to do this, and wp_safe_redirect() works fine to redirect to local urls only. In your callback function check for the $_GET[‘activated’] flag or you may get a “too many redirects” type of error. add_action( ‘after_switch_theme’, ‘my_theme_redirect’ ); function my_theme_redirect() { if( isset( $_GET[‘activated’] ) ) { wp_safe_redirect( admin_url(‘admin.php?page=alecaddd_sunset’) ); … Read more
First question: Is this a good practice? Based on the type of value you are saving, array as settings value is definitely good practice. How can I do this for a value within an array ex. get_option(‘header’)[‘header_logo’][‘image’]? If you believe option value for header might be empty or not saved, you can use this – … Read more
There’s always a character limit, but option_value is LONGTEXT so unless you anticipate more than 4GB of data you should be fine. I’d suggest json is unnecessary – you can save a PHP array as the value and it will be serialized/deserialized automatically. That said, as Tom points out, this is really micro-optimising, and won’t … Read more