You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I couldn't find my defined JS template in the HTML document. According to this post that in order to render the JS template it has to be registered via $wp_customize->register_control_type( $control_type ); and I found out that there's an issue with Kirki_Init class.
The kirki_control_typeshook didn't apply the filter I made and after applying this change (http://take.ms/iEZZT), the JS template is successfully rendered.
Version used:
3.0.25
Using theme_mods or options?
theme_mods
Code to reproduce the issue (config + field(s))
add_action( 'customize_register', function( $wp_customize ) {
/**
* The custom control class
*/
class Kirki_Controls_Notice_Control extends Kirki_Control_Base {
public $type = 'notice';
public function render_content() {
?>
THE CONTROL CONTENT HERE
<?php
}
public function content_template() {
?>
FIND ME SOMEWHERE
<?php
}
}
// Register our custom control with Kirki
add_filter( 'kirki_control_types', function( $controls ) {
$controls['notice'] = 'Kirki_Controls_Notice_Control';
return $controls;
} );
} );
The text was updated successfully, but these errors were encountered:
pkvillanueva
changed the title
Filter kirki_control_types bug, can't render Underscore template
Filter kirki_control_types bug, new control can't render Underscore template
May 11, 2018
Issue description:
I couldn't find my defined JS template in the HTML document. According to this post that in order to render the JS template it has to be registered via
$wp_customize->register_control_type( $control_type );
and I found out that there's an issue with Kirki_Init class.The
kirki_control_types
hook didn't apply the filter I made and after applying this change (http://take.ms/iEZZT), the JS template is successfully rendered.Version used:
3.0.25
Using theme_mods or options?
theme_mods
Code to reproduce the issue (config + field(s))
The text was updated successfully, but these errors were encountered: