38439 comments found.
Hello, the Visual Composer is not working with the latest WordPress update. I can edit any pages of my website … Can you please advise quickly on how to fix this?
Many thanks
Hey – you need to update to the latest version of Salient 7.0.8. In the current version of the theme, Salient Visual Composer v 4.11.2 is available which is the only version compatible with WordPress 4.5. Once you’ve updated Salient, head to the plugins section of your admin panel to update Visual Composer
Cheers
I’ve just installed the new version of the theme, and tried updating the VC plugin as well. It reports that it is updated successfully, but the version still prints as 4.9.2
Installed version: 4.9.2 Minimum required version: 4.10 Available version: 4.10
I’ve completely removed the VC plugin and reinstalled it, but that produces the same result.
And now i get the following error:
Installing Plugin: Salient Visual Composer To receive automatic updates license activation is required. Please visit Settings to activate your Visual Composer.
If i click settings i get a permission error..
Hey, the current version of VC included with 7.0.8 is 4.11.2 – if you’re unable to install that please open a ticket in regards with your admin credentials so I can take a look at what’s going on 
themenectar.ticksy.com/
Hello. Is there any auto-update notification or license purchase to put some were?
Thx
Hey, when you use the Envato toolkit plugin you can update from the dashboard if desired
When trying to insert an icon from the Font Awesome font set, using the shortcode generator, all I get is a bunch of squares:
The same squares are now showing on my site, where there used to be icons.
I have just updated both Salient and the bundled version of VC. The problem was there before and after the update.
BTW the other font sets work just fine. Only Font Awesome is squared.
Hey, have you verified that no plugins are causing this? If so please open a ticket in regards with your admin credentials so I can take a look at what’s going on themenectar.ticksy.com/
It seems like the “Toolset Views” plugin is to blame. I will contact the developer. Thank you.
Did a little digging into this issue, and apparently the “Toolset Views” plugin loads it’s own version of Font Awesome, causing a conflict. I’m not exactly sure how to fix this, but I saw that the version bundled with Salient is not the newest (being 4.6 – Salient is bundled with 4.2). Perhaps you could update this in the next release? Maybe it would have an effect.
In the meantime, do you know if/how I can load the newest version myself?
I contacted the plugin developer. Apparently they don’t provide Font Awesome in the frontend, but only in the backend. They seem to think it’s a theme issue. That it has something to do with the way Salient is enqueuing Font Awesome. Please see this thread: https://wp-types.com/forums/topic/font-awesome-conflict/
I’m not sure how to see how Salient is enqueuing Font Awesome, but perhaps you could help me with that?
Hey, I’ve noted to test further with it for the next update
Cheers
I’ve written back and forth with the developer of Toolset and he came to this conclusion:
This is a brighter Problem, involving many plugins that are required by your Theme.The issue is also not on Toolset site but comes from the JS File “ace.js” which is a File added by “js_composer_salient” Plugin
Please inform your theme developer about this.
That Plugin is throwing a Error to the console, which is the cause most certainly for this conflict.
It uses “window.controllers” which should not be used anymore.
And in fact, you will see complete different Icon placeholders depending on your Browsers.
You can read the full conversation here: https://wp-types.com/forums/topic/font-awesome-conflict/#post-390982
Crossing my fingers that you can fix this is the next update
Did you ever have a chance to look at this issue? The problem still persists 
Hi, the Visual Composer is not working with the latest WordPress update. Can you please advise on how to fix this?
Thanks
Hey – you need to update to the latest version of Salient 7.0.8. In the current version of the theme, Salient Visual Composer v 4.11.2 is available which is the only version compatible with WordPress 4.5. Once you’ve updated Salient, head to the plugins section of your admin panel to update Visual Composer
Cheers
Hi. Im having an issue getting the Nectar Slider to display full screen. It did, until I updated. Also, if I select the header to force transparency, the off canvas menu link doesnt work. Any Ideas?
Hey, please share your URL in regards so I can take a look at these issues for you
hi, thanks its http://sharonmcinerney.co.uk – So now, ive just ticked permenant transparency and the full page is working, but the logo is now gone and the off canvas menu wont work. This is utterly baffling. If I un tick the transparency, the menu works but full screen doesnt. I know you’re busy guys, but heeeeelp!
Cheers! Andy
Hey – please open a ticket in regards with your admin credentials so I can take a look at why the fullscreen issue is occurring https://themenectar.ticksy.com
Can you have a look at my ticket please?
Hey, could you please share the ticket ID so I can take a look
The Visual composer is not working on the latest downloaded version of this theme. However, when i tried the same on my local server, it worked fine. What could be the possible reason? Is there an issue with theme’s visual composer?
Please let me know.?
Hey – have you updated your Salient VC to the current version (4.11.2) in your plugins section after updating Salient to 7.0.8?
Cheers
When using Salient 7.0.8 child theme, there is no more site logo on site, swithing to non child theme, everything is ok, problem started after updating to WP 4.5.
Hey, do you have a modified header.php in your child theme? Please share your URL in regards
For anyone having the issue with an older version of salient, and has too many custom modifications to update to latest version without causing a lot of issues. Here is the solution:
Find /js/init.js file in the theme folder.
find this line of code: $(’.wpb_column[data-hover-bg=#]’).each(function(){
replace it with this:
$(’.wpb_column[data-hover-bg=”#”]’).each(function(){
Hey! I just updated to the recent version of the theme and noticed that the Salient options (typography, layout, footer, general, etc) that were in the sidebar are now gone. Did they relocate or is something F’d?
Hey – could you verify that none of the plugins you have active are causing the issue?
You guys rock. Thank you for the quick response and great support. It was a plugin! “WP Simple Pay Pro for Stripe” was the plugin culprit. All good now.
Cheers
I have a full width slider on my homepage that I do not want to loop forever. From your options I think I have it set right to no loop but it continuously loops after the “slides” end.
Hey,
Looping on the Nectar Slider refers to the slides repeating in an infinite fashion with the first coming after the last to the right and the last coming before the first on the left – stopping an autorotation after one go would actually need a javascript mod to the nectar-slider.js file as of now
Cheers
I’ve installed the theme and without making any modifications, I’ve set up a sample product page where the item quantity + and – signs show on each side of the quantity value whereas in the E-Commerce demo, the + and – signs are styled much better, on top of each other on the right side of the quantity value. What is the cause of this – or in other words; how can one achieve the same styling?
Hey – in your Salient options panel > WooCommerce tab select the “Add to cart text on hover” Product style
Cheers
Thanks. However, this time the shop page becomes undesirable. Is there a way to have the best of both worlds? Like; item quantity +/- buttons “Add to cart text on hover” style and shop page thumbnails “Add to cart Icon on Hover (Classic)” style?
That style is attached the alternative product style – combining them would require modding the woocommerce/content-single-product.php file as of now
vincidesigns thank you for your tips, I’ve updated the theme with envato toolkit and removed SVC, then checked appearance, install plugins and new version of SVC was there ready to install. Checked both the website I’m working on and the pages and everything looks good so far.
Hey – i’m glad you got everything working
Cheers
I’m using a much older version of Salient and the wordpress update to 4.5 affected my visual composer. I’m wondering, if I update to the 7.0.8 version by uploading this theme, is that going to completely destroy everything I’ve customized on my site and on my pages?
Hey,
If you’ve made modifications to the core files they will be overwritten – however theme settings and WP content will persist as usual with updates. Which version are you currently on?
Cheers
help me please!!
Hey – what are you looking for help with?
On the nectar slider i have the option not to loop. But after setting the autorotat speed it still loops after the last slide. Is there away to have it hold on the last slide?
Hey,
Looping on the Nectar Slider refers to the slides repeating in an infinite fashion with the first coming after the last to the right and the last coming before the first on the left – stopping an autorotation after one go would actually need a javascript mod to the nectar-slider.js file as of now
Cheers
Where do I upgrade to version 7.08? It only shows 7.07 in the download area.
Hey – the current version on here should indeed be 7.0.8, have you tried updating via the envato toolkit plugin? http://code.tutsplus.com/tutorials/toolbox-of-the-smart-wordpress-developer-the-envato-wordpress-toolkit--cms-23883
Cheers
Just updated to Wordpress 4.5 & Visual Composer is broken. Followed instructions in this thread deactivated then deleted the Visual Composer plugin. Downloaded Salient from ThemeForest website, tried to upload salient.zip in the themes > Add New but says “Destination folder already exists. /wp-content/themes/salient/ Theme install failed” there’s another step you need to tell people. Do I have to delete all salient files on the server manually by FTP…
Part 2… logged in via FTP to my site went to wp-content > themes > and renamed salient to salientOLD then went back to Wordpress Add Theme and salient.zip loaded fine this time. Then went to Plugins > install new plugin and ticked Salient Visual Composer (version 4.11.2) which was successful then I clicked ‘Activate’ kept settings as default. Also had to go back to Appearance > Themes and activate my child-theme. All good – my site is almost back to normal – except looks like the social media shortcode is still broken…
ThemeNectar… you can see this if you go to this page on my site for example http://www.guitar-planet.co.uk/jackson-x-series-soloist-sl3x/ the social media section top right has gone all weird… any ideas on a fix for that or is it supposed to be a visual update for social media?
Hey,
That social media redesign was implement a while ago when twitter changed their api to not longer serve share counts – have you tried to clear your cache? It’s looking normal to me on my end so it’s possible a half cached old version is showing on yours
Cheers
hi, i wanna buy this theme… is god for wordpress 4.5? or not?
As long as you’re using the latest Salient Visual Composer (v4.11.2) there shouldn’t be any issues
Cheers
Can’t you just provide some instructions on how to modify the theme files to fix without having to update? As you can see, many people have made edits, or are running older versions.
Hey – please see my response to your other comment in regards
You didn’t provide any solution. I have solved it with my developer. Yes, it is completely related to Jquery. Jquery has changed the way selectors work, so your theme had an . It’s very simple, you now have to add quotation marks around a hash.
The culprit is in your ini.js
this line:
$(’.wpb_column[data-hover-bg=#]’).each(function(){
needs to be changed to:
$(’.wpb_column[data-hover-bg=”#”]’).each(function(){
It’s too bad you couldn’t simply post this. My developer solved it in 10 minutes.
Hopefully this helps others that cannot update to the latest version.
Hey again, I saw the error appearing in the console on your site but as I said I couldn’t replicate it on my end at the time as I mistakenly thought that line still existed in the current version where it’s actually slightly different. I’m glad you got it sorted before I was able to take a further look though
