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
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
As i can see, your inputs are all the same (textbox) and most likely return the same type of data ( some human-readable text ), so i don’t think you need different functions. One will do it all, unless you have checkbox, radio buttons, HTML input, etc which might need different types of sanitation (such … Read more
It’s always a good idea to sanitize values being accepted from the user. A WP_Customize_Cropped_Image_Control will populate its associated setting with an attachment ID. Thus you could use absint as the sanitizing function. Remember that esc_attr is an escaping function and should only be used when printing out a value to the page, and here … Read more
I found the line of code in my theme that is breaking the customizer in 4.9. Behold! $wp_customize->remove_setting( ‘header_textcolor’ );
Yes, it’s possible to change the color and other CSS properties of a section and panel title/link. You just have to figure the CSS selector. Here’s the selector pattern for section and panel. #accordion-section-SECTION_ID_GOES_HERE .accordion-section-title { /* add CSS properties here */ } #accordion-panel-PANEL_ID_GOES_HERE .accordion-section-title { /* add CSS properties here */ } Say, you … Read more
I didn’t really used Customizer, but what you need is called „conditional display” (at least this is the term used in ACF & co). That being said, I found this article that may help you: https://florianbrinkmann.com/en/3783/conditional-displaying-and-hiding-of-customizer-controls-via-javascript/ Also, this SE topic: Is it possible to conditionally displaying and hiding of customizer controls for each device preview?
Re: Question 1 At first I was thinking you were wanting to use the active state to manage the disabled state but I see that is not the case. Anyway, since you are already toggling the notification then the best suggestion is to just toggle the disabled state of any inputs at the same time: … Read more
So I finally have it. The problem came from the php.ini configuration option filter.default. The option was set to: filter.default = full_special_chars filter.default_flags = 0 As explained in the PHP documentation, this had the effect of sanitizing and stripping characters from all $_POST, $_GET, $_COOKIE, $_REQUEST and $_SERVER data, effectively beating me in the back … Read more
After adding your custom control class, you need to register your control like below code, then you can call your control via JS function prefix_customize_register( $wp_customize ) { $wp_customize->register_control_type( ‘TestControl’ ); } add_action( ‘customize_register’, ‘prefix_customize_register’ ); Then via JS, like this: api.control.add( new api.Control( ‘birthdate’, { type: ‘test-control’, label: ‘Birthdate’, description: “Someone was born on … Read more