Given a setting with an ID of “foo” you can obtain the value via: var value = wp.customize( ‘foo’ ).get() To ensure that the setting is registered before you attempt to get its value, you can use this deferred pattern: wp.customize( ‘foo’, function( setting ) { var value = setting.get(); // … }); This should … Read more
There isn’t really much of a difference for the default controls. Using the Class is needed for using custom built controls. So basically your first example is the short form of the second one only available for core controls. For details have a look at the documentation.
The easiest way is to just hide it with CSS. For example: #customize-control-custom_logo .button.remove-button { display: none; } The harder way would be to subclass the image control JS and omit the remove button from the template, but this seems overkill.
There is a simple way to do this by using __return_false . The downside is you get a double refresh as it checks for a partial and then returns “false” which results in a full refresh. This is problematic if you are using javascript only to show a “realtime” preview. In that case, you’d have … Read more
What you need to do is implement a custom Partial in JS which applies a custom refresh behavior of modifying the background-color instead of fetching a newly-rendered partial from the server. So it’s partials with edit shortcuts but without any server-side selective refresh. For example, enqueue the following JS in the customizer preview with a … Read more
If you’re after getting custom CSS ontop of WordPress’s Admins Customizer buttons, inputs, and controls – you can do something like this: add_action( ‘admin_enqueue_scripts’, function(){ $screen = get_current_screen(); if ($screen->base == ‘customize’) { wp_register_style( ‘custom_wp_admin_css’, plugins_url( ‘your-file.css’, __FILE__ ), //get_template_directory_uri().’your-file.css’, false, filemtime( plugin_dir_path( __FILE__ ) . ‘/your-file.css’ ) // get_template_directory() . ‘/your-file.css’ ) ); wp_enqueue_style( … Read more
In order to interact with the event “widget-added” , you should enqueue your JavaScript file using “customize_controls_enqueue_scripts” to avoid it being part of the repetitively loading preview iframe ( where $(document) is different from the parent page document). I was able of interacting with the “widget-added” event using this example : in theme’s functions.php function … Read more
You can use the global $wp_scripts and global $wp_styles; to get all registerd scripts and styles. Eg. All Scripts // All Scripts global $wp_scripts; $all_scripts = array(); foreach( $wp_scripts->registered as $script ) : $all_scripts[$script->handle] = $script->src; endforeach; // echo ‘<pre>’; // print_r( $all_scripts ); // echo ‘</pre>’; All Styles // All Styles global $wp_styles; $all_styles … Read more
WP_Customize_Color_Control takes 3 parameters: /** * @param WP_Customize_Manager $manager Customizer bootstrap instance. * @param string $id Control ID. * @param array $args Optional. Arguments to override class property defaults. */ The problem with the original code is that you’ve passed the same Control ID (link_color) to two separate instances. So, the most recently added control … Read more
You can either: A: Use Posts rather than Pages. WP enables Categories on Posts by default, so it’s easy to select a Category for each Post (all categories are shown with checkboxes, or it’s easy to add a new one). B: Use Pages, and create a custom “Page Category” taxonomy to categorize them, which also … Read more