There are about 17 new updates compared to the visual composer built into Salient.
If there is an option to disable the inbuilt version and use the full version, then at least it should work. Please give us a solution as we rely on features of the full version but there is a big compatibility issue with Salient.
Disabling the inbuilt version and enabling the full version gives a blank white screen.
Unfortunately as soon as I activate the standalone plugin, the frontend of the website turns white. The error given is:
Fatal error: Call to undefined method
WPBakeryVisualComposer::getInstance() in
/var/www/vhosts/domain/httpdocs/wp-content/themes/salient/functions.php
on line 126
So I've commented out all of the "if (class_exists('WPBakeryVisualComposerAbstract')" statement. Error does not show but I don't know if this will affect Salient's fundamental functions. If you could please clarify this, I'd be greatful.
I've managed to fix it somewhat by commenting out "main VC styles" from salient\nectar\assets\css\nectar_meta.css.
Still not sure if this will negatively affect Salient's fundamental features. Please check my previous updates to this thread and let me know if what I've done is safe :) Thank you ever so much for your support .
Hey again! That's really odd - after you renamed the wpbakery inside of Salient did you also ensure that the option to disable the Salient VC was still active in order to ensure that the code wasn't still trying to get called?
Also, your mod shouldn't effect anything else outside of VC so you're safe in that regard :)
Yeap - I did just that but it seems the stylesheet was still affecting VC. Right now I've got raw VC running fine - albeit all the nectar integration is gone of course. The nectar dropdown is sufficient for now I guess.
There are about 17 new updates compared to the visual composer built into Salient.
If there is an option to disable the inbuilt version and use the full version, then at least it should work. Please give us a solution as we rely on features of the full version but there is a big compatibility issue with Salient.
Disabling the inbuilt version and enabling the full version gives a blank white screen.
Hey Fahim,
After you disable the one in the theme - renamed the folder "wpbakery" in the theme to anything else to allow the standalone plugin to activate :)
Cheers
Unfortunately as soon as I activate the standalone plugin, the frontend of the website turns white. The error given is:
Fatal error: Call to undefined method WPBakeryVisualComposer::getInstance() in /var/www/vhosts/domain/httpdocs/wp-content/themes/salient/functions.php on line 126
So I've commented out all of the "if (class_exists('WPBakeryVisualComposerAbstract')" statement. Error does not show but I don't know if this will affect Salient's fundamental functions. If you could please clarify this, I'd be greatful.
Actually... here's how VC backend editor looks when using the standalone..
Even on the frontend editor, the add elements box doesn't even show. Unusual. I hope there'll be a new version of Salient soon with the latest vc.
I've managed to fix it somewhat by commenting out "main VC styles" from salient\nectar\assets\css\nectar_meta.css.
Still not sure if this will negatively affect Salient's fundamental features. Please check my previous updates to this thread and let me know if what I've done is safe :) Thank you ever so much for your support .
Hey again! That's really odd - after you renamed the wpbakery inside of Salient did you also ensure that the option to disable the Salient VC was still active in order to ensure that the code wasn't still trying to get called?
Also, your mod shouldn't effect anything else outside of VC so you're safe in that regard :)
Cheers
Yeap - I did just that but it seems the stylesheet was still affecting VC. Right now I've got raw VC running fine - albeit all the nectar integration is gone of course. The nectar dropdown is sufficient for now I guess.
Thanks for the reassurance!
Interesting - thanks for the additional information. I've noted to test with this again for the next release.
Cheers :)
Awesome - I look forward to the next release... very eagerly :)