Support » Plugin: Kirki Customizer Framework » Please fix at least 3(!) bugs

  • Resolved wpdude777

    (@wpdude777)


    Hi!

    I would like to use KIRKI, but it seems it is so buggy for real project? i have found 3 problems for 1 day of using (latest version of WP, Kirki (downloaded from wordpress.org), i’m using theme_mods):

    1) “Reset” button doesn’t work for Spacing control https://github.com/aristath/kirki/issues/1160

    2) “Reset” button causes JS error if i use Typography control:

    VM26792 customize.php?return=%2Fwp-admin%2Fadmin.php%3Fpage%3Dfw-settings:142 Uncaught SyntaxError: Unexpected token <

    3) Typography control has a bug with font-variant. Try to change font to “Oregano”, and choose variant 400, then change font to Yatra One (it has only “regular” variant but i get “400” variant from previousl selected font through get_theme_mod function, not “regular”)

    as i see, there is no support on GithubPages? Please guys, help to fix this ASAP, i spent few working days on Kirki and it will be sad to start looking for another plugin if this doesn’t work as described

    • This topic was modified 6 years, 4 months ago by wpdude777.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter wpdude777

    (@wpdude777)

    p.s. KIRKI embedded in the theme

    Plugin Author Ari Stathopoulos

    (@aristath)

    1. Fixed in the development branch on github
    2.

    VM26792 customize.php?return=%2Fwp-admin%2Fadmin.php%3Fpage%3Dfw-settings:142 Uncaught SyntaxError: Unexpected token <

    That suggest a PHP error, can you please check your log and let me know what the issue you’re getting there is exactly?
    3. 400 and regular are the same thing on google-fonts (and webfonts in general).

    as i see, there is no support on GithubPages?

    Yes, there is. I help as much as possible.

    Plugin Author Ari Stathopoulos

    (@aristath)

    Marking as resolved due to lack of a response from the original poster in more than a month.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Please fix at least 3(!) bugs’ is closed to new replies.