The widgets section ID is “widgets”. Here’s info for all the default Customizer sections/panels: Site Identity – title_tagline – 20 Colors – colors – 40 Header Image – header_image – 60 Background Image – background_image – 80 Navigation – nav – 100 Widgets – widgets – 110 Static Front Page – static_front_page – 120 all … Read more
It’s been a while since you wrote, but I was having the same problem and your question allowed me to solve it, so thank you! I was going crazy trying to figure it out. I am working from Underscores, as it looks like you are, and the fix was to change the script’s version number. … Read more
Looks like you are missing some things from the settings array, namely type need to be theme_mod here and capability should be set too. You can try: $wp_customize->add_setting( ‘woocommerce_productdisplay’ , array( ‘type’ => ‘theme_mod’, ‘capability’ => ‘edit_theme_options’, ‘default’ => ‘1’, ‘transport’ => ‘refresh’, ‘sanitize_callback’ => ”, ) ); Also note default for a checkbox should … Read more
This live preview code should be like this – wp.customize(‘inspection_cta_text’, function(value){ value.bind( function(to) { $(‘.footer-cta’).text(to); }); }); Basically you don’t need the “em”. And there always should be default value present in the theme mod. For example – .footer { border-top: solid 1px #<?php echo get_theme_mod( ‘background_color’, ‘#fff’ ); ?>; } In your case it … Read more
You’re registering the option in the customizer as an option and then trying to get it as a theme_mod. If you simply change the type from option to theme_mod when you’re registering the setting it’s gonna work fine. So try using this code: add_action(‘customize_register’, ‘h2c_customize_register’); function h2c_customize_register($wp_customize) { $wp_customize->add_setting( ‘logo_width_px’, array ( ‘default’ => ”, … Read more
<style> tag accepts all the global HTML attribute, including class and id. So, you could do something like this: wp.customize( ‘custom_css’, function( value ) { value.bind( function( newval ) { if ( $(“#my-custom-style”).length > 0 ) { $(“#my-custom-style”).remove(); } $(‘head’).append(“<style id=”my-custom-style”>”+ newval + “</style>”); } ); } );
If you check out the source of WP_Customize_Control::__construct: public function __construct( $manager, $id, $args = array() ) { $keys = array_keys( get_object_vars( $this ) ); foreach ( $keys as $key ) { if ( isset( $args[ $key ] ) ) { $this->$key = $args[ $key ]; } } // [redacted] } So you can see, … Read more
I think you work about the ajax call. Inside the theme, in the right frame works all default WP functions inside the loop. But if you get the post inside the customizer you can use the ajax call and get the id from the URL. Source Example JavaScript add_action( ‘wp_ajax_fb_custom’, ‘fb_customizer_ajax’ ); function fb_customizer_ajax() { … Read more
Short answer: No, your settings will not be deleted. They will be available next time you install the theme. Long answer: There are 2 ways a theme can store its settings in the database: options and theme_mods. If they use options, then inside the wp_option table in the database there will probably be an option … Read more
The relevant line that generates that link in wp-includes\class-wp-customize-nav-menus.php is $description .= ‘<p>’ . sprintf( __( ‘You can also place menus in <a href=”https://wordpress.stackexchange.com/questions/248853/%s”>widget areas</a> with the “Custom Menu” widget.’ ), “javascript:wp.customize.panel( ‘widgets’ ).focus();” ) . ‘</p>’; and the more relevant part of it javascript:wp.customize.panel( ‘widgets’ ).focus();” ) so it seems like the key for … Read more