Hello,

This means you are using another plugin that uses the same class as our tagdiv mobile theme. 2 plugins that need to use the same code will not work. Please choose which one you need to use, the tagDiv mobile theme or the other mobile plugin you have installed. In these cases both will not work.

If you need further assistance our support team will be happy to help with any requests on our official support forum at http://forum.tagdiv.com/forum/newsmag/

Thank you! Bogdan B

Hi,

That may happen as long as the TD composer is active. From what I know there is a note of this on our list and it will be investigated. If it is required to hide elements, you could use CSS media queries to hide them, which is basically the same thing as the WPBakery settings do. Sorry for the inconvenience.

Thank you! Simion C.

Thanks for the reply Simon. Yes Tagdiv composer is active. It is my understanding with latest version that Tagdiv Composer has to be activated otherwise theme breaks.

I’m keen to update my main site with latest version of the theme but am happy to wait for an update that addresses the issue.

Quick question, my main site is on Newsmag 4.7 and WP 4.98. What is the latest version of wordpress that 4.7 version of Newsmag supports?

Thanks again, keep up the great work.

Hello,

Newsmag should be compatible with all WordPress versions as we have not identified any issues on our testing platforms.

Thank you! Bogdan B

Thanks Bogdan B. I have tested the latest version of the theme and the issue of hiding elements on mobile using WPBakery Composer still exists. Will you be addressing in next update?

Thanks, Regards Ryan

Hello,

Sorry for the inconvenience but wpbakery will receive no further implementation from us as it remains just an alternative solution. Each new theme implementation will be made through the tagDiv Composer. If you need to hide items, you will need to use alternative solutions.

Thank you! Bogdan B

Thanks Bogdan, I appreciate the quick reply.

If I’m honest that is not the answer I was hoping for.

I purchased this theme as it was bundled and compatible with WPBakery Composer, and there was always the option to use either WPbakery composer or the tagdiv composer. I chose WPBakery Composer.

I use WPBakery composer with Newsmag and many other sites as it is very good and I am very familiar with using it.

While I’m sure Tagdiv composer is great, we’ve used WPbakery composer across our site, to build pages and to display content in articles for the past two years. I have more than a thousand articles in this time with Newsmag WPbakery shortcode in articles/posts.

An example here at bottom of page where we insert recent articles in content https://www.mcnews.com.au/yamaha-tmax-560-review/ using WPBakery

Will this WPBakery shortcode now break in future updates to the theme?

I already now can’t update my theme to the latest version because of WPbakery composer does not work correctly with that version as mobile elements no longer hide when specified to.

I should not have to use ‘alternative solutions’ as you suggest. This is really poor solution that you are offering a customer that is totally leaving me in an untenable position.

Can I suggest that your team continually support the product as it was originally sold to your customers?

If your team want to focus on Tagdiv Composer, that is fine, but why take theme support away for WPBakery Composer?

This will cause a lot of issues for us as well as many of your other customers that might have invested heavily in building their sites/content with Newsmag and WPbakery Composer.

I hope that your team can reconsider.

Thanks

Regards

Ryan

Hi Ryan,

Unfortunately you are not using WPBakery as intended at all. From the very start we advised users not to use wpbakery on posts as shown here: https://forum.tagdiv.com/how-to-use-visual-composer/ The guide clearly states the plugin only works properly on pages. It was never tested on posts.

You need to keep in mind that technology progresses and things change. You bought the theme way back in 2016 and you cannot expect things to stay the same. As an example, a phone from 2016 would not work with current apps as the OS version would be too old and not support newer apps. That is why we need to keep up with the times as newer updates contain newer technologies that wpbakery simply does not support. That is why we have decided to move on with our own page builder that can keep up with the times. It was a decision our developers took moving forward with our themes. WPbakeryis still part of the theme package and was not removed specifically for cases such as yours but we cannot provide any more implementation for this plugin.

If you need further assistance our support team will be happy to help with any requests on our official support forum at https://forum.tagdiv.com/forum/newspaper/

Thank you! Bogdan B

Hello Bogdan.

Thanks again for the reply.

I have been using WPBakery Composer for many years. This plugin explicitly is designed for using in pages, posts, and custom posts types.

Using WPBakery Composer in Posts is half of this plugins functionality, with the other half using it in pages.

Why would I, or anybody else need to refer to your documentation to check if WPBakery Composer has compatibility with posts? It’s obvious that it does.

As I mentioned, the plugin is designed for use with pages and posts. Any prospective Newsmag customer would assume that it works and has been tested with Newsmag for all functionality, not half, seeing as it is bundled with Newsmag

Why would your team bundle a plugin but not test if the plugin works for use in posts – of which is part of core function of this plugin?

To be clear, despite your teams lack of testing with WPBakery in posts, WPBakery works just fine in posts with Newsmag and has donen for years.

As mentioned 2 months ago, and today, I can no longer hide specific elements on my Home PAGE (not post) using WPbakery with any version above 4.7 of the theme. Why? And why have your team not fixed it?

Thanks again

KInd Regards

Ryan

In response to your tech progress example, this is very poor.

If an OS is outdated, you update the OS. The reasons why the phone from 2016 might not work with latest apps is simple, and due to the phone manufacturer stopping their updates. That is called forced obsolescence, to force the consumer to buy a new phone.

Besides you are also using hardware as an example. In this context, we have no hardware, as we have WordPress, Newsmag, and bundled plugins.

The plugin WPbakery has sold 388,000 times on Codecanyon and is bundled with almost every theme on themeforest. I am sure that their developers are doing their due diligence to stay current and on top of latest practices.

Like I said, your team are free to move in a different direction with Tagdiv composer but you should continue support for WPbakery but your team are choosing not to.

In your next theme update, please can you fix this bug/issue so that I can hide PAGE elements on my Home PAGE using WPBakery.

I am stuck on Newsmag version 4.7 and can’t update to any later releases.

Where was my warning that you’d just suddenly stop supporting WPBakery Page builder?

Thanks

Regards

Ryan

OK Ryan.

I will pass this on to our development team.

Thank you! Bogdan B

Anye news? I have tried the latest Theme and Bakery Composer update and still can’t hide VC elements using responsive options.