Compatibility with Visual Composer

  • sugardaddy

    (@sugardaddy)


    8 years, 9 months ago

    Very nice plugin ! Really. It saves us from creating duplicate content with a different url.
    We found an issue with Visual Composer. In VC we can add some CSS inline in a dedicated box. I don’t know how it’s linked to the page. This content (yeah we think it’s content ;-)) is not copied to the cloned version. That’s not the worst : when viewing the draft version of the cloned page, this (the inline CSS) is not parsed at all and we can’t view the real version of the content’s design. We can still have an external CSS file so it’s not a blocking issue.
    If you can help… it’ll be appreciated.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Inderpreet Singh

    (@inderpreet99)

    8 years, 9 months ago

    Hi,

    We have not tested our plugin against Visual Composer (commercial plugin), so I can’t speak on exactly what Visual Composer does in the background.

    If Visual Composer is storing postmeta, you must register the post meta keys with BU Versions plugin. BU Versions will automatically copy those on clones and overwrite when publishing. We have an example on how to do this: https://github.com/bu-ist/bu-versions/wiki/Adding-Post-Meta-Support-for-Alternate-Versions

    Thanks.

    Thread Starter sugardaddy

    (@sugardaddy)

    8 years, 8 months ago

    Well, thanks a lot. I didn’t thought at this.
    Yes Visual Composer store postmeta but registering it don’t do anything. Is there something more to do ?
    Here’s the code :

    function foo_register_alt_version_features( $features ) {
	$features['vc_post_custom_css'] = array(
		'_wpb_post_custom_css',
	);
	return $features;
}

add_filter( 'bu_alt_versions_feature_support', 'foo_register_alt_version_features' );

    Thanks a lot for your help.

    But… that doesn’t explain the second issue : these custom CSS are not parsed in alternate pages. Sorry for the double issue 😉

    Thread Starter sugardaddy

    (@sugardaddy)

    8 years, 8 months ago

    Could you please juste validate the code in my previous message ?

    And I discovered that the custom styles at the elements level are not parsed too when previewing alternate pages.

    Thanx

    Thread Starter sugardaddy

    (@sugardaddy)

    8 years, 8 months ago

    Answer of the support about this : “If we are not wrong, you are referring to the design options CSS which is applied for the element. This is generated at run-time and is not stored in the database. Same is the case with page custom CSS.”

    So I don’t know how it is stored… we’re f…

    However I know some plugins that do cloning and the custom CSS of VC are being cloned too. But what’s interesting in your plugin is the kinda sort of staging state. So, I hope you’ll take some interest to VC in the future even if it’s a commercial plugin (not sure but you can try to get a free version in order to be compliant with their plugin)

    • This reply was modified 8 years, 8 months ago by sugardaddy.
    • This reply was modified 8 years, 8 months ago by sugardaddy.
    Thread Starter sugardaddy

    (@sugardaddy)

    8 years, 8 months ago

    We encounter too many bugs so we decided to uninstall.
    We’ve found another plugin for staging the content and it clones everything, including what we missed. Hope it will suits our needs. You can find more on it here : https://ww.wp.xz.cn/plugins/revisionize/

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Compatibility with Visual Composer’ is closed to new replies.