[RadModerator]

Hi William,

Yes, I’ll pass your concern. 🙂

Every project start from nothing even our beloved X theme, so is cornerstone. We will never reach its peak if we will never start it. And yes there are more to improve but that’s part of it. Cornerstone creation is not just an overnight decision, it’s based from different opinion and issues we’re getting from older versions. One of the reason are issues brought by bundled plugin which we can do nothing since it’s not ours and it takes weeks and months waiting fixes and updates. Cornerstone is not free from issues just like the other, but it’s more favorable than not able to fix them since it’s not ours. Furthermore, as you can see from many comments here and other places online, Cornerstone is a big hit among the vast majority of our users.

Cornerstone is a required plugin which should be installed. But it doesn’t mean you’re required to use cornerstone builder. You can still use VC or other builder, and if you really wish to disable cornerstone builder then you can simply go to Admin > Settings > Cornerstone and toggle off the post type.

And yes, there are more feature requests and enhancement that needs to be addressed. But they can’t be implemented in same time. It would take time like week, months, or years.

I’ll quote your statement and I will respond from my point of view,

But when we talked to the owners or developers of these plugins they went extra miles to make their plugins work with your theme, which really was not their faults because their plugins were working just fine with other themes.

They did not implement integration to our theme. It’s us who provide integration to their plugin (eg. VC). They only provided the API that we could use so we can integrate it to our theme, like shortcode mapping. They will not spend time developing integration just for specific theme, what they do is provide general fixes and standard functions that every theme could use. And it happens that X theme has its own set of shortcodes. While other theme don’t have their own shortcodes or elements and they just rely from VC’s shortcode and element. Like you can just use Twentyfifteen theme and just install VC with no problem.

Because X theme has its own shortcodes then it’s a good decision to make X shortcodes have its own builder separate from VC which have its own too.

Thanks for understanding.

[William YParticipant]

This reply has been marked as private.

[RadModerator]

Hi there,

I understand where you coming from. And thanks for your thoughts, appreciate it 🙂

And yes, we do recommend cornerstone builder, but not necessarily we wanted everyone to use it. Everyone is free to use their preferred builder.

If definition of being premature is because it’s not better than the other or before, then the question is when should we? Even great software has their flaws up to this date. If we will wait, then we could never release is because flaws and improvement are never ending process.

If the question is why so early, it’s because we need to improve sooner without any limitation from outside features. And to do that we need to remove the bindings as early as possible. Again, it’s not mandatory.

X4 is a big step forward, not just related to any visual changes or feature changes. It’s more related to structure overhaul in preparation for more coming feature. We can’t stay in older structure when your target feature will not fit anymore.

I do develop wordpress theme and plugins too, and I did use many frameworks. Though we may have different definition of theme framework. If the theme finish all the jobs while just letting me do the clicking, then I personally call it a theme and not a theme framework. A framework for me is something you can port or extend to another functionality freely with a set of standards that user should follow.

True, a theme and plugin should work along without tweaking. But you probably saw many themes and plugins that you can’t just install because they are incompatible, else, there is no need for updates just to fix them. And it’s nothing to do with wordpress standard, they are simply incompatible. We do expect that not all plugins are compatible to our theme and we’re trying to solve it as much as possible. But that doesn’t mean that we should stop. And I’m pretty sure that all plugins from wordpress directly are not all compatible to other themes that you’re referring (unless it’s just a plain theme with no other functionality than just being a theme).

Thanks for the discussion 🙂

[RadModerator]

Hi William,

I checked again and looks like I accidentally hit the wrong edit link and pasted content. Sorry about that, will check if it can be retrieved. Though, not sure what happened.

Thanks again!

[William YParticipant]

🙂 🙂 🙂

[William YParticipant]

This reply has been marked as private.

[RadModerator]

Hi William,

I’m not sure if we can answer that yet, but in my personal opinion is should be fixable. What you could do is don’t apply the fix directly to the theme as much as possible. Do it in child theme as templates can be overridden through child theme, while functions can be re-declared at child theme’s functions.php, then filters/hooks/action can also be removed/re-added through child theme’s functions.php

Compatibility should depends on the one who will do it because it’s the main purpose of customizing it, to make it compatible 🙂 . Though, I’ll try to help if it’s something easy to tweak which might also benefit us getting more information for this request.

Thanks.

[William YParticipant]

This reply has been marked as private.

[RadModerator]

Sure, you can always switch back to X when you needed. Thanks!

[Author]

Posts