Hi there,
I probably will make you sigh with this question but i give it a try anyway.
Since the introduction of the TagDiv Composer i’ve been wondering what to do. Previous questions did not give me useful answers. I’m very insecure about what to do.
I will try to specify my questions and i hope someone can help me out…
1. In the online tutorial about switching from WPbakary to TagDiv Composer it says:
“Step 2 – The page has to be recreated using the new page builder. You will have to build a new page and edit it with the tagDiv Composer replicating your original page (made with Visual Composer).”
There is no way that i’m going to rebuild all the pages on my website. If that is really nescessary i have to switch to another template soon.
a. What will happen when i do nothing?
b. How long will you keep updating and supporting WPBakery?
2. What will happen to my site if i de-activate WPBakery or when the plugin stops working (for any reason)? Thus: without replacing it by TagDiv Composer.
3. Can i keep WPBakery working on my existing pages and create new pages with TagDiv composer? In that case i will have to activate both plugins. Will that cause problems?
4. Not really a question, but when you like you are welcome to explain why i should use the new composer? What’s in it for me?
I hope you can answer this questions for me. Thanks in advance.
Hi,
I might give you few answers until tagDiv support reply.
You cant use tagDiv Composer and WPBakery Page Builder at the same time. It breaks pages layout. On other hand, tagDiv claims that pages made in WPBakery Page Builder should (but they arent 100% sure so they dont claim full compatibility) should work fine in tagDiv composer and I tested that, they do work for me. At least homepage (havent tested all pages on my web sites)
You cant deactivate WPBakery Page Builder without activating tagDiv composer since its essential to building your page. I mean you can deactivate, but your page will not render and you have to activate eather WPBakery Page Builder or tagDiv composer. I just deactivated WPBakery Page Builder on one of my web pages to grab a screen shoot for you http://prntscr.com/lrr2g5
I dont know how long they will keep supporting WPBakery Page Builder but I presume they will continue to do it for long time since there is a lot of people that dont want to switch. But how long they will continue to update it, I dont know. So far Im not satisfied how often they update it https://forum.tagdiv.com/topic/why-you-arent-updatind-wpbakery-page-builder-with-new-version-on-your-theme/# but you should be fine even if you dont update it at all if there is no major bugs found in WPBakery Page Builder
tagDiv composer have much more options than WPBakery Page Builder so switching to it will give you chance to set some stuff that you previously had to use custom CSS, etc. But for me tagDiv Composer is not user friendly at all and is hard to find options, etc and I just dont like to build pages in it. And I have to add that in my test, I havent seen any difference in site speed if I built it in one or other builder but I have pretty fast hosting
I hope this helped you
Thanks pcservis. Your reply provided some great insights. I appreciate it.
Still no reply from TagDiv.
I gave you more precise answer than they will 🙂
Hi,
@pcservis That would sum it up, good explanation.
There are no plans to exclude or stop providing the WPBakery page builder with the theme. We will not pressure users to switch composers, use one or the other and there will be no problem. WPBakery will be updated same as before, when the theme is updated.
1. It would be necessary in most cases. The exception would be pages that contain only theme provided page builder elements like blocks and grids (which work in both composers). If there are specific WPBakery items and you would deactivate this plugin, only shortcodes will appear.
2. If the WPBakery plugin would not be active anymore, and the tagDiv composer is active, it can handle theme elements (blocks, grids etc) but not specific WPBakery elements (tabs, accordion, masonry grids etc).
3. Both can be active, but it may cause problems with some elements or WPBakery row layouts and settings. For example single images or image elements may not display properly, to name one. There were other issues before, we solved as many of them as we could.
4. Most of the new features since the tagDiv composer introduction are created specifically for it and will work only with it. The cloud library plugin will work only with our page builder.
Basically you can keep using WPBakery permanently or for as long as you want. There are no plans to stop including it in the theme package, or stop updating it.
Thanks
