TagDiv,
My team and I just wondering what’s your contingency with other clients like us who have hundreds of posts/pages created using Visual Composer for years and that are having issues with transitioning to TagDiv composer? I’m pretty sure we are not the only one and we are curious if you have any contingency of not losing clients with this issue.
As you already know, there are some conflicts with using the tagDiv composer if pages/posts were originally created using Visual Composer. In our case, we have hundreds or even thousands of pages and posts that were built in VC. Some elements are not working when we tried to convert it to tagDiv Composer. We can’t afford and don’t have the time to manually fix each page/post.
So again, how did you envision this change for clients using Visual Composer that has hundreds or thousands of pages/posts?
Hi,
Indeed there seems to be some problems between tagDiv Cloud library and WPBakery, we recommend to use only one of them with tagDiv Composer, in this case you need to use WPBakery and deactivate the tagDiv Cloud library.
We have a little guide for how to “migrate” from a builder to another -> https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/ but if you have a lot of pages made in WPBakery, maybe it will be better to continue with it.
If you already using the plugins in this way, please let as know all the problems/bugs you are facing, in this way we can recreate theme and try to provide some fix for these problems.
To make sure that the problems are only between tagDiv Composer and WPBakery, please deactivate the rest of the plugins and let us know the problems that are occurring and how we can reproduce them, also some screenshots or a link where we can check theme we be helpful.
Thank you for your understanding!
Until when you will be keeping Visual Composer along side TagDiv Composer?
Hi,
For the moment there are no plans to remove the plugin from our theme, but if someday it will come to this, we’ll make an announce for these changes.
Thank you!
