• Hey Noor,

    I Wanted to install your plugin but am unsuccessfull, the reasom for me was testing if you changed the VC composer check within your init scripts.

    At the moment you check for VS like this

    if ( is_plugin_active( 'js_composer/js_composer.php' ) ){
    
    /* Constants */
    define( 'ASVC_URL', rtrim( plugin_dir_url( __FILE__ ), '/' ) );
    define( 'ASVC_DIR', rtrim( plugin_dir_path( __FILE__ ), '/' ) );
    if ( ! function_exists( 'prime_WordPressCheckup' ) ) {
        function prime_WordPressCheckup( $version = '3.8' ) {
            global $wp_version;
            if ( version_compare( $wp_version, $version, '>=' ) ) {
                return "true";
            } else {
                return "false";
            }
        }
    }.......
    else {
        function asvc_required_plugin() {
            if ( is_admin() && current_user_can( 'activate_plugins' ) &&  !is_plugin_active( 'js_composer/js_composer.php' ) ) {
                add_action( 'admin_notices', 'asvc_required_plugin_notice' );
    
                deactivate_plugins( plugin_basename( __FILE__ ) );
    
                if ( isset( $_GET['activate'] ) ) {
                    unset( $_GET['activate'] );
                }
            }
    
        }

    This check does not take custom install locations for VC in account which a lot of themes use. Uncode for example is like is_plugin_active( ‘uncode-js_composer/js_composer.php’ ) I think if you would get the Bool like this
    if( defined( 'WPB_VC_VERSION' ) ) { ... } Your plugin should be compatible with all VC installations, as an added bonus you should be able to check if the VC version is not too old.

    If you fix it i will but the plugin, and your potential market is suddenly 30% larger ??

  • The topic ‘Compatibility with custom wpbakery / VC themes’ is closed to new replies.