Version 11.4.2 no longer compatible with WPBakery Page Builder

Posted in: Newspaper
Post count: 5

Theme version 11.4.2 is not compatible with WP Bakery Page Builder.

We have set 3 columns in a page but in the front end it was not displaying 3 column content. Also, the “Hide on Device” feature is also not working. Please check attached screenshot – https://www.awesomescreenshot.com/image/25415988?key=17b5e3b7c080e0759f22bd3b24b4e651

While we have corrected the issue the best we can with CSS, we’re concerned further issues like this will compound.

Here’s a live link to an example page with the issue. This page has already been correct with CSS: https://generationiron.com/power-30-2020/

The CSS fix we implemented is as follows:
#post-79815 .td-pb-span8.vc_column_container { float: none; margin: 0 auto;}

#post-79815 .td-pb-span8.vc_column_container img {
width: 100%;
}

Can you kindly check all column settings and please provide a fix or patch?

Post count: 27744

Hello,

The plugin is in our theme, but we do not longer recommend it to use it. We have long recommended using only a one-page builder, not both, because some options in tagDiv Composer may no longer work due to WPBakery => https://i.imgur.com/O4CA0y0.png -> https://i.imgur.com/bFnzNtQ.png -> https://i.imgur.com/mv8AhFU.png -> https://i.imgur.com/IMyLYiY.png

Thank you!

Post count: 5

I wanted to follow up on this because we’re experiencing more issues with WPBakery. Per your comment above, you said “The plugin [WPBakery] is in our theme, but we do not longer recommend it to use it. We have long recommended using only a one-page builder, not both, because some options in tagDiv Composer may no longer work due to WPBakery.”

We built our whole site using WPBakery because it was originally included in your theme. We have 125 published pages and 13,935 posts. Do we need to rebuild all our posts and pages using tagDiv Composer? Or can we simply deactivate tagDiv Composer to stop the conflict?

It’s my understanding that if we deactivate the tagDiv Composer plugin (to prevent the conflict), the theme will not fully work (resulting in more conflicts).

We understand that having both page builders active causes a conflict. We don’t want to run both page builders – we want to only use WPBakery since that’s what was originally included and was the page builder used to create 124 pages and 13,000+ posts. However, it seems that you’re forcing everyone to use tagDiv Composer, and that your page builder plugin is causing a direct conflict with the previous page builder plugin you included and supported.

Can we just deactivate the tagDiv Composer plugin to resolve the conflict, or is that plugin required for the theme to function properly? Can you please provide some insight?

  • This reply was modified 4 years by encoda.
Post count: 27744

Hello,

I’m sorry, but from the very beginning, we recommended WP BAKERY only for pages, not for posts, because from the beginning this functionality has not been tested -> https://i.imgur.com/CpUnFkr.png -> https://forum.tagdiv.com/how-to-use-visual-composer/
Also, in the beginning, we did implementations with WPBAKERY, but before we had our page builder, but after that, we didn’t do implementations with WP Bakery, but with tagDiv Composer, we only did small fixes for it, nothing more.
I don’t know if it would be a solution to disable tagDiv composer, because all the theme features are now in tagDiv composer.
What we can help you with is CSS code, if it can solve it.

Thank you for your understanding!

Viewing 4 posts - 1 through 4 (of 4 total)
The forum ‘Newspaper’ is closed to new topics and replies.