Since Update to Newspaper 6 i’m missing some important elements of Visual Composer (f.e. Fronted Edit etc.) I have activate all items of shortcodes and deactivated all Plugins. I also made a new installation of the theme. Unfortunately without success. Curious is, that the missing elements appear when I change the template to another one! When I change back to Newspaper6 the elements disappear again.
Does anyone have a solution to this problem?
Thanks
Frank
Hi,
Did you followed this guide to upgrade from version 4? – https://forum.tagdiv.com/how-to-update-the-theme-2/ and also did you run the script to rename shortcodes(like it is suggested in the documentation).
Or do you refer to the Visual Composer elements from backend? – http://screencast.com/t/B2ExxHCzXQye Please make sure that you select all elements from Visual Composer settings – http://screencast.com/t/i33Um4pq
Please provide more details about this as I’m not sure what you mean.
Thanks!
Hi,
thanks for your quick response. I installed the Newspaper6-Theme now for three times. Before this i deleted the old theme and the VC. I select all elements from Visual Composer settings. The result is every time the same, there are missing some elements is VC (see attachements).I’m desperately and don’t know what to do anymore.
I hope the screenshots show you, what i mean.
Kind regards
Frank
Hi,
You can try to remove this condition from booster functions – http://screencast.com/t/fhBlRO6R but I also asked the developer about this and it is recommended by Visual Composer developers to have this function in the code.
Thanks!
Hey!
I am another “Frank” but I am experiencing similar problems.
I had VC (full license) installed at my site prior to purchasing Newspaper 6.
We have installed according to the manual (https://forum.tagdiv.com/update-the-visual-composer-plugin-wpbakery/)
We tried several times.
We are constantly having a persistant error message in our dashboard (“Important notice: You have an outdated version of Visual Composer Design Options. It is required to review and save it.”) that we can not get rid of and we are lacking a good number of elements (http://screencast.com/t/B2ExxHCzXQye) from VC. We are missig everything in that screensho after “Masonry Media Grid” (see here: abload.de/img/vctes4b.jpg )
We also tried turning everything off and on again – didn’t help.
For us Visual Composer is only offering the same four Dashboard-options as Frank showed in his screenshot above.
Any ideas?
Thank you in advance,
Frank B.
Edit.
By pure randum luck while reactivating plugins I hit (in dashboard) “Visual Composer” -> “Settings” and in there by a stroke of sheer luck I accidentaly clicked “user group access rights” -> “Administrator” and guess what? Almost all Newspaper-related items were disabled…
For the persistant Error-Message: that one is still there.
I strpngly suggest adding this to the knowledge-base to check there
Hi,
I will add this on our list to be specified in the documentation how to enable all Visual Composer elements, as I see that many users have this issue. Glad that you managed to solve this!
Thanks!
I’m glad I could help.
But still: What about that nagging Error-Message in Dashboard? How to get rid of that one?
(see attached image)
http://abload.de/img/open_design_optionsfysng.png
– Frank.
Hello,
You can update your theme to the latest version 6.5.1 so it can support the latest version of visual composer, and you can also update the plugin : https://forum.tagdiv.com/how-to-update-the-theme-2/ – https://forum.tagdiv.com/how-to-update-visual-composer-plugin/
Please make sure you only install the visual composer version that is bundled with the theme.
Thank you!
Thank you for coming back to this.
We have Newspaper 6.5.1 and the plugins that came along installed. The problem is occuring with Newspaper 6.5.1.
We installed AND updated according to your documentations.
Twice.
Thank You!
Hello,
Normally the message should not appear with the visual composer version that comes with the theme. The message you see may be due to the fact that you had the full license of V.C. prior to this version. You can either ignore the message or try to contact the plugin developer to explain the situation and see how the message can be removed.
Let us know how it goes!
Thank you!
