This topic has 4 replies, 2 voices, and was last updated 10 years, 5 months ago ago by Eva Kemp
Hi there,
I’m having a problem with my site the last 10 days.I got a message from my hosting provider that said tha some file url in my wordpress site was creating spam and they had to disable it until i deleted it/fixed it.
That url was related with Visual Composer as i can understand,specifically the url was /wp-content/plugins/js_composer/assets/lib/jcarousellite/system.php .
They told me that this might have happened because the plugin is an older version and not the latest.This problem happened 2 times in 10 days although i deleted the bad files,so im rather frustrated.
I ‘ve just updated my theme to the latest version but the plugin is still the old version 4.1.2.
Is there a way you can provide the latest version 4.2.3 of WPBakery Visual Composer any sooner please? Why should i pay extra to buy it,if this was not mentioned several months ago when i bought the theme?
Best regards,
Gianna
Hello,
To update the plugin you need download the theme archive at http://themeforest.net/item/legenda-responsive-multipurpose-wordpress-theme/5888906 where we’ve recently included the updated versions of plugins VC and Revolution Slider. After you unzip the archive you’ll find the plugins in legenda/framework/plugins directory. Upload the new version via FTP and remove the old one.
Regards,
Eva Kemp.
This was so helpful,i finally was able to update the plugins!I had no idea i could find them in that folder,i thought they would be more obvious like the woocomerce plugin in previous updates,so my mistake!I hope this solves my website’s security problem.
Thank you for the fastest response,
Best regards,
Gianna
You’re welcome.
We’re glad you were able to update the plugins.
If you have any questions, don’t hesitate to contact us.
Regards,
Eva Kemp.
Tagged: latest version, problem, solution, templates, visual composer, woocommerce, wordpress
The issue related to '‘Visual Composer problem with not having latest version’' has been successfully resolved, and the topic is now closed for further responses