Why have you ruined such a great plugin?

  • Resolved rzepak

    (@rzepak)


    1 week, 4 days ago

    I’ve been using Kirki for over a decade. It used to be one of the best lightweight Customizer frameworks out there with 500k active installs, that wasn’t exactly a niche opinion.

    I’ve spoken directly with Ari, the original author, so I understand why he had to sell the project. What I don’t understand is what happened next. You essentially abandoned it and now, after four years, you come back with a page builder?

    No one asked for yet another page builder bundled into Kirki. That’s not what made it valuable, and it completely misses the point of the project.

    Worse, this release is full of bugs and has caused serious issues across existing sites. You’ve effectively broken thousands of websites that relied on Kirki being stable and predictable.

    This direction is baffling.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Nafiz

    (@urnafiz)

    1 week, 3 days ago

    Hello @rzepak,

    Thank you for sharing your feedback. We truly understand your concerns.

    Our intention with this update is to expand Kirki’s capabilities for users who prefer a more modern, flexible way to design their websites, while keeping performance a top priority. That said, we understand this direction may not align with everyone’s expectations.

    We sincerely apologize for any issues this release may have caused. Stability is extremely important to us and we are actively working to address reported issues. If you are experiencing specific issues, please let us know. We are here to help and will do our best to resolve them promptly.

    We appreciate your long term support and honest feedback.

    Best regards,
    Nafiz | Kirki Support Team

    Plugin Support wprashed

    (@wprashed)

    1 week, 3 days ago

    Hi @rzepak

    I hear your frustration — especially given your long history with Kirki. Changes like this can be disruptive, particularly when you’ve relied on something being stable for years.

    That said, as the current maintainers, we do have to make decisions about the direction of the plugin, including larger architectural changes. We understand that not everyone will agree with those choices.

    Regarding the issues you mentioned: many of the reported errors are happening on sites where themes or bundled integrations haven’t been updated in a long time, and are not yet compatible with the newer Kirki structure. That said, we’re not dismissing the impact — we’re actively reviewing all reported bugs and working through fixes where they’re needed.

    We genuinely appreciate the feedback, even when it’s critical. It helps us identify where things are breaking in real-world use and improve stability moving forward.

    In the meantime, if stability is critical for your current projects, sticking to a known working version (such as 5.2.3) is a safe temporary approach until compatibility updates are rolled out.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.