Hi there,

built-in plugins can't be updated as frequent as standalone versions and can't be updated for ever. That said it will still get updated, although if you need to stay up to date with the plugin I suggest considering buying the standalone version either.

Regards
djwd

Alright, sorry for making it confusing.

If you own the VC plugin already and try activating it, it will cause a conflict, that's true, so the reply I gave you earlier on TF comments is the one I usually give to this question. My point is that if you specifically need to always be up to date with the latest VC version for whatever reason, I can tell you how to disable the built-in version so you can use the standalone version instead.

Regards
djwd

Removing/comment out this block from functions.php should work (around line 260)

/*
==========================================================
PAGE BUILDER INITIALIZATION
==========================================================
*/
	
$dir = dirname(__FILE__) . '/inc/';
 
$composer_settings = Array(
    'APP_ROOT'      => $dir . '/js_composer',
    'WP_ROOT'       => dirname( dirname( dirname( dirname($dir ) ) ) ). '/',
    'APP_DIR'       => basename( $dir ) . '/js_composer/',
    'CONFIG'        => $dir . '/js_composer/config/',
    'ASSETS_DIR'    => 'assets/',
    'COMPOSER'      => $dir . '/js_composer/composer/',
    'COMPOSER_LIB'  => $dir . '/js_composer/composer/lib/',
    'SHORTCODES_LIB'  => $dir . '/js_composer/composer/lib/shortcodes/',
    'default_post_types' => Array('page', 'post')
);
 
require_once locate_template('/inc/js_composer/js_composer.php');
 
$wpVC_setup->init($composer_settings);

// Disable unwanted modules
wpb_remove("vc_teaser_grid");

Of course incompatiblies of new versions won't be supported though until they're included with PowerMag.

In case of theme update you would need to do this again.

Hope this helps,
djwd