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
Let's say I have a setting: my_theme_option[color_accent].
In your script, you split them to check every node. When it runs check if ( ! _.isUndefined( wp.customize.instance( currentNode ) ) ) it will always return false. Because there is no wp.customize.instance( 'color_accent' ).
The correct check is for wp.customize.instance( 'my_theme_option[color_accent]' ) instead.
I think this would work fine on theme_mods mode, as there is no split process to the setting key.
Can you please try the develop branch and let me know if it works for you now? It should be ok, I just pushed a fix for this.
Using options instead of theme_mods is no something a lot of people do - and for good reason - so it doesn't get tested by many people.
Thank you for reporting this issue!
Fix will be included in 3.0.17
All my color controls suddenly not working on:
WordPress 4.9
Kirki version 3.0.16
When you change the value of color control, there is error message shown in console:
from
.../kirki/controls/js/dist/script.js?ver=3.0.16:504
Looks like the
foundNode
is never set, because the checkif ( ! _.isUndefined( wp.customize.instance( currentNode ) ) )
never returnstrue
.Please help
The text was updated successfully, but these errors were encountered: