This is what I see: http://clicky.strapr.com/image/3L1G3t1b4404
Yet when I click through it says I need to have purchased it from within the envato marketplace. Are you going to introduce a way for us to automatically update this “Required” plugin without having to do it manually? This is a huge PITA.
You can’t manually update the plugin; it’s a free “bundled” version, which is tested and contains compatible custom modules for the theme.
The version included with the theme is updated when major theme updates are released.
You cannot update the commercial paid version to work with the theme, as they may not have all the same functions and because the version included with theme is optimized for the theme.
Not rally a PITA as you have no need to update every dot revision of the plugin to add features not included with the theme or tested to even work properly.
Just because an update is available doesn’t mean you need to have it!
See the theme docs for more info
https://forum.tagdiv.com/how-to-update-visual-composer-plugin-wpbakery/
Hope that helps !
Chris,
It’s not a PITA if I don’t have to manually update it. Meanwhile, WordPress says it wants to update even though I clearly cannot use the built in update tool. Ideally you would call this “free” version something different and remove it’s ability to check for updates from the standalone version in future releases.
Here is what I see in the updates page: http://clicky.strapr.com/image/1a0H1e1K3d1W
Yes, WordPress “reports” and update is *available* but you don’t need to have it. You can just ignore it. Nothing earth shattering is going to happen if that notice is there, and your site isn’t going to stop working if you don’t have that.
Actually, the theme folks *do* put in code to stop the “nag screen” from showing up, but the people at VC keep changing their product, and so that keeps coming back when it really shouldn’t.
You can’t change the name of the product/as it’s a licensed version, so that is why it must be installed and activated as a normal plugin. Blame the VC folks for how they license this to theme developers, and not the theme folks. With the hundred different theme houses bundling VC with their themes, it’s a great product, but this is one of those annoyances.
Yes, you *do* need to manually update it if/when a new version is provided with theme update. You don’t need to update the plugin unless you plan to keep changing your layouts again and again.
So, again, see the theme documentation regarding how this works.
TIP: when you see an update available – do NOT just go and update it – go check and see if it has problems, breaks something else, etc. — for instance, one Disqus update added a cross scripting vulnerability, one version of Yoast SEO broke a whole bunch of things and took 5 fixes in a week to sort that out; AddThis plugin added a blank 10px space at bottom of every page on websites; took 6 weeks to fix. Etc.
Just because a new update is shown in the update panel does NOT MEAN YOU NEED TO INSTALL IT. This is part of learning the WordPress ecosystem.
Sorry if this neither helps or educates, but thought I’d share for anybody else freaking out about the topic. It’s really a non-issue.
from the theme docs:
How to Update Visual Composer plugin (WPBakery)
•The theme includes a license for this plugin so you don’t have to buy it.
•You don’t have to activate the plugin license, it’s already activated.
•You can’t update the plugin directly from the it’s producer.
•You don’t have to worry about the plugin update warnings.
Chris,
The real issue is that theme creates a false positive that an update is available. It shouldn’t do that.
Regards,
Lane
Yes, as stated:
Actually, the theme folks *do* put in code to stop the “nag screen” from showing up, but the people at VC keep changing their product, and so that keeps coming back when it really shouldn’t.
I have one website where I have 3 nag items right now; but all 3 have bugs and so can’t be updated until fixed; so I just ignore them. I concentrate on the content, SEO, growing readership and get on with my life. Highly recommended. You’ll go nuts worrying about the pesky updates.
I agree. Kind of annoying, though. But not strictly a “theme issue” — but a plugin issue, and Tagdiv does their best to work around that.
Whew! I’ll shut up about this now! 🙂
