When I post in a page without using visual composer, the text appears in white even if I hightlight and choose black. I am not able to edit a text widget using Visual Composer.
Hello!
Unfortunately, there is no way to “convert” the pages because there is a conflict between TagDiv Composer and WP Bakery.
Please check our guide to know how to shift from WPBakery to Composer: https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/
TagDiv Composer contains a lot of functions and features, please check our tutorial here: https://forum.tagdiv.com/tagdiv-composer-tutorial/
Documentation here:
– https://forum.tagdiv.com/cloud-library-templates/
– https://forum.tagdiv.com/design-post-pages-using-cloud-library-templates/
– https://forum.tagdiv.com/cloud-library-category-templates/
Check also our video tutorials here: https://www.youtube.com/c/tagdivThemes/videos
Thank you for understanding!
For some of us customers, we bought Newspaper back in the day when you guys used WPBakery as the primary page builder for your theme. It appears that you guys decided to create your own page builder (which is fine), but you did it in a way that is no longer compatible with the previous page builder you guys included with your theme.
What are your older customers supposed to do when we’ve built hundreds of pages using the page builder you originally provided, and it’s no longer compatible now because you guys decided to create your own page builder which directly conflicts with it?
You guys offer no way to convert anything. The theme does not work now without your page builder plugin being active. And when your tagDiv Composer is active, it overrides and breaks the previous page builder you included with the theme.
I don’t understand how you guys think this is okay? I have no problem with you guys introducing an additional page builder as an alternative, but a new page builder that breaks the old page builder and is directly incompatible?
Also, the link above on “how to shift from WPBakery to Composer” does not work. The whole situation just seems really unacceptable. Why should be people buy this theme or continue to use it knowing you guys might decide to introduce another new page builder in a couple years that breaks the previous page builders we’ve all built our sites with?
Hello!
I understand your thoughts.
Unfortunately, you can not use 2 builders in the same time. If you want you can use the WP Bakery without the TagDiv Composer.
I gladly recommend you to shift from WPBakery to Composer, because WPBakery is an old builder plugin. Please check those screenshots to know how to shift from WPBakery to Composer: https://www.screencast.com/t/6xLVMmlsY ; https://www.screencast.com/t/zWHrRmK1LQC ; https://www.screencast.com/t/vuFdT9Stx ; https://www.screencast.com/t/DWbSf3qj ; https://www.screencast.com/t/QuHyGccTK71v
Thank you for understanding!
Per your comment, “If you want you can use the WP Bakery without the TagDiv Composer.”
When we deactivate TagDiv Composer, the site breaks and we see td shortcode everywhere So as much as we want to use WPBakery without TagDiv Composer, we cannot.
We understand there’s a conflict when using 2 page builders. The problem is there’s an even bigger conflict when we go to deactivate TagDiv Builder.
If we can use WPBakery without TagDiv Composer as you suggest, can you please show us how or provide instructions?
I am not using WP Bakery. The plugin is not in my dashboard.
I am not able to publish text to my website unless it is in an article. I cannot edit any text on a page. When I add the Tagdiv widget “Column text” to a page, I cannot edit the text. This is happening on several of my Tagdiv websites.
