I think this is what you are looking for . $cats = get_terms(‘category’); $blog_cats = array(“all” => “All”); foreach ($cats as $cat) { $blog_cats[$cat->name] = $cat->name;} Then to show this <?php echo aq_field_select(‘category’, $block_id, $blog_cats, $category); ?>
When you register a setting, you pass the santize callback for that setting: register_setting( ‘my_setting_group’, ‘my_setting_name’, // The next parameter is the validation callback ‘my_setting_validation’ ); Then, in the validation callback you can allow whatever you want. For example, in the next code snippet, users with unfiltered_html capability will be allowed to insert raw HTML … Read more
You need to hook your function to the admin_menu action: add_action( ‘admin_menu’, ‘wpt_add_theme_page’ );
Better to avoid such a thing. The settings API has two “faces”, one the UI, and the other is handling the form submission. The form submission is handled on a different URL than the UI (/wp-admin/options.php) and therefor your “user action” depended code will not run and the handling of storing the setting in the … Read more
The escaping function is adding it, esc_url guarantees that what it returns will be a URL, as it’s an escaping function, and so it should, if you’re outputting a URL you should use esc_url so that it’s safe and definitely a URL and not something else maliciously snuck in. The confusion here though, is that … Read more
Instead of saving the default values to the database, you can retrieve them from the class by using a helper method something like the following: /** * Get the option that is saved or the default. * * @param string $index. The option we want to get. */ public function get_settings( $index = false ) … Read more
So I could understand why you “customized” (i.e. use your own version of) the do_settings_sections() and do_settings_fields() functions — because you want to use div and not table, right? But if it’s just about styling, you could actually just use CSS to style the table so that it doesn’t look like a table; however, you’ll … Read more
The options are not being saved correctly because you used the wrong input name — it should match the second parameter for register_setting(). So for example, with register_setting(‘myplugin_options_group’, ‘api_username’), the input name should be api_username, but then you used myplugin_api_username. Additionally, it should be noted that screen_icon() has long been deprecated.
You don’t need a separate rule in your .htaccess. Add … define( ‘WP_CONTENT_DIR’, ‘YOUR_LOCAL_PATH’ ); define( ‘WP_CONTENT_URL’, ‘YOUR_PUBLIC_PATH’ ); … to your wp-config.php. Do not write into wp-settings.php. This file will be overwritten during the next update – never touch a core file.
The settings API can be puzzling 😉 Replace: do_settings_sections( ‘ia_section_id’ ); with do_settings_sections( ‘srchild’ ); to display your defined settings section. The general usage is: do_settings_sections( $page ); where: $page (string) (required) The slug name of the page whose settings sections you want to output. This should match the page name used in add_settings_section(). Default: … Read more