The issue, as determined by Chip Bennett in our conversation above, was related to the settings_errors() call. The problem was that I didn’t specify a setting for which I wanted to display either errors or update notices mostly because the tutorial from which I was working didn’t either. By specifying that setting, I see one … Read more
It depends on what the fields do. If they are all of the same type – a label and a text input for example – then, yes, that’s a good approach. You can just use the sixth parameter to create a different output. But if these fields are different, need different escaping methods (esc_textarea() versus … Read more
The two are not the same thing at all, and likely you’ll use both. The Administration Menu stuff shows you how to create the menu item and page for your settings to live on. In other words, the menu item in the left hand bar, and the existence of the page itself. The Settings API … Read more
Consider everything that comes with a vanilla WordPress installation a core file. Core files will be overwritten on updates, so it’s not safe to edit them. E.g. wp-config.php isn’t a core file, because the vanilla installation comes only with the sample version of that file.
Given that you are dealing with email, I’d run wp_kses() with a very limited $allowed_html array similar to this sample from the Codex: array( ‘a’ => array( ‘href’ => array(), ‘title’ => array() ), ‘br’ => array(), ’em’ => array(), ‘strong’ => array(), ); HTML rendering is even more squirrelly in email readers than browsers … Read more
$callback = NULL means there is the $callback variable but it has no the value. In this case, unless you add any setting fields by add_setting_field() and register those settings by register_setting(), you’ll get the Settings subheader on the Settings page without any content in this section. Here is an old tutorial which can be … Read more
Because you mentioned the Settings API I assume you want to do AJAX from the admin area of wordpress. You have some research to do, so my answer is to check out these: http://dobsondev.com/2015/06/12/wordpress-ajax-example/ https://pippinsplugins.com/custom-database-api-reasons-for-custom-tables-and-an-api/ That should get you where you need to go. Happy WordPressing!
The problem here is that you never created $ppk_fields as a global variable. $ppk_fields = [ ‘field 1’ => [ ‘title’ => ‘Fieald One’, ‘type’ => ‘text’, ‘section’ => ‘section_1’, ‘default’ => ‘default’ ] ]; Here we have a variable that is created normally, and obeys normal scoping rules. It isn’t a global variable, and … Read more
The problem is that in your calls to selected() you haven’t set the 3rd parameter to false. For both selected() and checked() if you don’t do this it will echo the attribute immediately, which won’t work properly if you’re using it inside a concatenated string. So change: selected( get_option(‘myplugin_admin_bar’), 1 ) To: selected( get_option(‘myplugin_admin_bar’), 1, … Read more
If I take the value sanitize_callback out of the argument array completely, everything works as desired, so error-free. Yes, and that’s because you used the wrong callable syntax which then causes PHP to use a global function named sanitize_options instead of the method/function of the same name in your class (i.e. Faqdesk_Settings::sanitize_options()). So to solve … Read more