Support » Plugin: Kirki Customizer Framework » my theme requires kirki and there is no update for wordpress 5.2

  • Resolved marciemeredith

    (@marciemeredith)


    Hi. I have site errors going on right now partly due to kirki plugin. My site was updated to the latest wordpress 5.2 and now this plugin says it has not been tested with this version of wordpress and my host says it is causing errors. When will you have an updated version? My theme has this built into it I guess, and I’m having major text and menu problems right now. Thanks

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Ari Stathopoulos

    (@aristath)

    Hello there @marciemeredith,

    You mentioned you’re getting errors? Could you please be specific? What are these errors?
    If your host is saying that the plugin is causing errors, could you please ask them to be more specific?
    I’d be more than happy to resolve any and all issues you may have, but I’ll need details in order to do that.
    Have you tried contacting the theme author? Kirki is just a framework, it provides useful tools to theme developers. However, how they use those tools and what they do with them in their themes is out of our control so the right course of action will depend on what the errors you’re getting are.

    As for the “not tested with this version of WordPress” message, the plugin HAS been tested with WP 5.2 and it works perfectly fine with it. The fact that it says it not been tested with WP 5.2 in the plugin page is simply because we can’t add “compatible with WP 5.2” before 5.2 is actually released and the last update was a month ago – so before the 5.2 release.
    WP 5.2 compatibility was planned well in advance, but we can’t just release an update only to change the “5.2 compatibility” message that WordPress shows, an update will be released when there’s some new feature to release, a performance improvement or a bugfix.

    Thank you for being so prompt! I think that the theme ended up being the overall issue and maybe how they had worked with the plugin or something. Sorry I am not knowledgeable about the specifics. But I think everything is resolved.

    Plugin Author Ari Stathopoulos

    (@aristath)

    I’m glad you managed to resolve your issue!
    If at any time you get more details about what the issue was don’t hesitate to post them here, others may also encounter similar issues so having as much data as possible is always a good thing 🙂

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.