Search Results for 'composer'

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?

• This reply was modified 4 years by encoda.

One more! I report the same problem. TagDiv is already giving me too many headaches, it’s less and less worth following. This adds to the bugs in query monitor (plugin) that has not been fixed either and is still at 218MG of RAM usage. Also floating menus have stopped working in the new version and everything that needs to be in sticky mode doesn’t scroll in visual composer mode.

Hello. Ok, i’ve done all that, still, i don’t see how. I’ve change the front page fonts, ’cause a can click on them, but i can not go into a single post from the tagdiv composer, it simply selects the block. thx.

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.

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 just discovered code already in the theme that accomplishes exactly what I am looking for, but it has been commented out by your team.

wp-content/plugins/td-cloud-library/shortcodes/common

/**
* on composer iframe and on templates that do not have posts we show the no posts message
* @see td_page_generator::no_posts() - this function generates the __td('No posts to display').
* the text can be overwritten by the template using the global @see td_global::$custom_no_posts_message
*/
//if ( tdc_state::is_live_editor_ajax() || tdc_state::is_live_editor_iframe() ) {
//$buffy .= td_page_generator::no_posts();
//} else {
//$offset = intval($this->get_att('offset'));
//if ( $offset === 0 ) {
//$buffy .= td_page_generator::no_posts();
//}
//}

Lines 1717 – 1724.

When uncommented, this block shows the “No posts” message as expected.

Is this intentionally commented out or was it a mistake?

I would like a way to preserve my update of uncommenting it so that I don’t have to re-do it during the next theme update.

Please let me know if this is possible.

Thank you,
Patrick

• This reply was modified 4 years by patrickrodo.
• This reply was modified 4 years by patrickrodo.
• This reply was modified 4 years by patrickrodo.