Hi there,
Thanks for sharing your feedback—this is a very valid use case.
At the moment, there isn’t an option or hook available to fully disable the builder. That said, I’ve shared your request with our team so they can consider adding this flexibility for developers like you in future updates.
Don’t worry—if any of your users run into issues related to the builder or Kirki, our support team will be there to help.
I presume this would apply to the “Design with Kirki” button that has appeared in the editor? I have no need of that, and wanted to disable it. I’m guessing it’s connected to what the OG poster asked about here?
Hello @joe-siegler
The new Kirki plugin includes a Page Builder with 100+ themes. Unfortunately, there isn’t an option available right now to disable it.
Right, I understand that, but…
in the message to Gnodesign it was implied that it could be a possibility in a future update – that’s what I was referring to.
Hello,
Got it, thanks for clarifying.
I understand what you’re referring to. I’ll make sure to pass your feedback along to our team so they can consider it for a future update.
Appreciate you taking the time to share this—it really helps.
A few years back I installed a theme on my blog which included a handful of plugins – one of which was yours. It just “came with” the theme I use, so the design aspects of all this are of little interest to me. Link: https://joesiegler.blog/
Hello @joe-siegler,
Kirki was used as a customizer framework by many themes, I am myself into your very same situation. It looks like the plugin has been taken over by other authors (or maybe same authors, I don’t remember), that (rightfully) decided to turn it into a fully fledged builder. It is annoying, because if you needed to use Kirki just like a customizer framework, you don’t need that at all. That’s what @gnodesign was asking, if an option to completely deactivate the builder will be available in the future.
@wprashed, even if I get your reasons, you need to understand that a lot of Kirki users will be annoyed by this move. It is okay to have an updated and secured plugin in the future, but we just don’t need all the bloats of a full website builder, if the only use of Kirki was as customizer framework. If you pursue this road, I won’t be surprised if “someone” decided to fork this to offer a lightweight solution, as it used to be. I’m confident you will think about it.
Hi @michael-travan
Thanks for sharing your thoughts—we understand your concern. Kirki has been widely used as a lightweight framework, and we know not everyone needs the builder.
Right now, there’s no option to disable it, but this feedback has been noted and shared with our team for consideration.
That said, the builder can be helpful for end users to design their websites with a modern approach, and it’s built to be faster than many existing WordPress page builders.
Appreciate you raising this.
It is clearly one of those decisions that ignores what the users want.
Which is okay, you can do that, it is free software, we have no rights to complain.
But be bold enough to admit that your product has pivoted and existing users concerns are ignored as a deliberate decision. There is no need to be wishy-washy with “At the moment, there isn’t an option or hook available to fully disable the builder.”. Whoever made this decision to turn a plugin that had purpose A to a completely different plugin serving purpose B must have made this decision knowing that it’ll put existing users into a situation they did not choose to end up in.
Again, it is fine, you can do that. But don’t pretend it is a fair thing to do.
I can tell you what it looks like: You had this plugin, installed on large number of sites, because it was a go to Customizer extension for developers for many years. It was obvioulsy not installed by end-users, it was used by devs. So looking at the large install base you just decided to effectively hijack all those sites and try to push you new and completely unrelated product onto those websites, hoping the end users would pick it up.
Again, you can do that, but don’t create this deeply unjust discussion suggesting the builder cannot be disabled “At the moment”. We all know what is going on.
You may be polite with your words, but is it really polite to think we are all blind / dumb to not see what you did? I don’t think so…
You can do whatever you want with your software, but you cannot at the same time expect us to pretend we don’t see what you did and to not speak up when you make a fool out of us all…
@wprashed: after reading all those complainings, I just have one question: Why I have since the last updates in my dashboard now a link named “Kirki” and can’t reach it as admin-user “Sorry you are not allowed to access this page”? wtf what are you doing here?
Kirki was a part of a theme, which I’m using since some years. I guess like all other here in this thread. Can you please explain, what’s going on here and why plugins got installed and restricted on the same way without any information?
-
This reply was modified 1 week, 1 day ago by
neralex.
Hello @neralex,
Sorry for the confusion and inconvenience this has caused.
With new update, we introduced builder feature in Kirki, which is why you are now seeing Kirki menu item in your dashboard. The plugin itself has not been restricted. Its a temporary permission issue. To resolve this, please deactivate Kirki plugin and then activate it again. This should restore proper access. We are already working on a fix and plan to include it in an upcoming release to prevent this from happening again.
