So… through some trial and error, I discovered that I’d gotten some of the logic wrong in order to detect and ensure the result of the API call (and subsequent state change) was treated properly. I suspect that “other” state changes were firing and I was unsubscribing before I needed to – hence the unsubscribe … Read more
As the names themselves seem to state, one of those hooks to the customize-controls, the other to the customize-preview. They are not the same and you could in fact use them both, for different purposes. If you’re hooking in JS code to affect the controls in the customizer, then you would want to use customize_controls_enqueue_scripts. … Read more
I also found that Cloudflare Rocket Loader would cause javascript errors in this situation. When the .js file was marked to be ignored, but the inline js was unable to be so marked, undefined errors would occur when the script tried to access the async-loaded inline data. The approach detailed in How to intercept already … Read more
When you register the setting in JS, you need to supply the current value saved in the DB as the value, not some default value. So instead of: var setting = new api.Setting( ‘mySetting’, ‘JS Default Value?’ ); You would need to obtain the value via some means like the REST API and then use … Read more
What you’re looking for is two things: The wp_tiny_mce function that loads all the needed JS etc The code below: This to setup the JS etc: // Setup the TinyMCE stuff and target it at our desired textarea wp_tiny_mce( true, array( “editor_selector” => ‘tinymce_class’ ) ); And this HTML where you need the editor box: … Read more
The nonce authentication method is only for requests made from within WordPress, as described in your own link (emphasis mine): It is important to keep in mind that this authentication method relies on WordPress cookies. As a result this method is only applicable when the REST API is used inside of WordPress and the current … Read more
Notice in the example that the tag does not have the type=”text/javascript” attribute. For some reason Rocket Loader requires data-cfasync=”false” to be used without the type=”text/javascript”… a bug? Your code does add the data-cfasync=”false” attribute, but does not override the WordPress behaviour of adding the type=”text/javascript” attribute also, which makes Rocket Loader not to “ignore” … Read more
Settings must be registered in PHP one way or another. If you don’t register them statically via $wp_customize->add_setting() calls, you will have to register dynamic recognition of them via the customize_dynamic_setting_args filter. Why? In order for a setting to be safely stored it must be sanitized and validated by the server. Relying on client-side sanitization … Read more
If you register your settings on the server then you do not need to register them on the client in JS, as this will be done for you. Here are some examples creating controls after you have created the settings: Customize Posts CSS Customize REST Resources Customize Featured Content Demo In the first example for … Read more
The following solution assumes that your plugins are using wp_enqueue_script() to insert scripts into the HTML code. If they don’t they are broken by design and we cannot change the script tag. This code works like the one in this answer, in fact, it is almost a duplicate … First make two lists of all … Read more