The header-text option in the custom header allows you to switch off the header text, not to change its content. You can change the header text in the customizer. To show it in your front end you must must use echo get_bloginfo(‘name’) for the blog title and echo get_bloginfo(‘description’) for the tagline.
If the customizer has been bootstrapped (that is, if the customize_register action has fired), then you can look at the control itself (assuming you flip your choices array, as I think your values should be the keys and vice-versa): $price = $wp_customize->get_setting( ‘price1’ )->value(); $control = $wp_customize->get_control( ‘price1’ ); $price_text = $control->choices[ $price ]; However, … Read more
First of all, When you uncheck Display Site Title and Tagline in the customizer, it doesn’t matter what value you’ve already put in Header Text Color, the customizer saves it as blank (not empty string, the actual text “blank”) after you Save & Publish. You may check this in wp_options table in the database after … Read more
The add_setting logic cant find the my_theme_sanitize_select function, you need to tell it where it is: ‘sanitize_callback’ => array( $this, ‘my_theme_sanitize_select’ ), remember that your function is inside a class so it cant just be accessed, add this to your class: public function my_theme_sanitize_select( $input, $setting ) { $from_parent = my_theme_sanitize_select( $input, $setting ); return … Read more
Since you are invoking the change callback directly: value.call( customize, func ); Since you’re not passing in the value, then newval will be undefined and $customStylesheet.text(newval) will do nothing. You need to pass in the value like so: value.call( customize, func, value.get() ); Nevertheless, it would be better to re-use the existing style element that … Read more
This is a terrible way to make sure you are in the right context. The normal way is to load your class only when it is really needed, not earlier. A side effect is that the following code cannot be cached, because that line is evaluated on run time, not on compile time. The same … Read more
Honestly for the select field it’s not so important what the choices are for sanitizing the field and in fact what you are doing I don’t believe is a good idea if a user wants to filter your settings to add new options to the select field. More importantly you are looking to sanitize the … Read more
The issue boils down to this bit of code in WP_Widget::display_callback(): $was_cache_addition_suspended = wp_suspend_cache_addition(); if ( $this->is_preview() && ! $was_cache_addition_suspended ) { wp_suspend_cache_addition( true ); } This gets called right before WP_Widget_Recent_Posts::widget() and its purpose is to try as best as possible for back-compat to prevent widgets previewed in the Customizer from polluting the object … Read more
I’m currently not able to write it all down for you but you can always use a sanitizer (WordPress has one build in) to add an # if its not present. Also as far as i know u always need to create a setting and a control. Like under here: $wp_customize->add_setting(‘Some_color’, array( ‘default’ => ‘#fffff’, … Read more
Lol, coming back to my own post 3 years later looking for answers. Deactivating plugins did nothing, but ended up finding WP_Customize_Code_Editor_Control which has options for code_type. So here is a manual method for adding a proper CSS editor to a theme. This probably only useful for updating older themes that were already installed. add_action( … Read more