Thanks for the quick response. I updated to 5.5.3 but the problem is still there. If I deactivate the visual composer plugin everything works dandy (of course my site looks like a**) but I don't get any error messages in the back end.
I think update to this version is not clear and a deeper step by step information is needed urgently.
First of all we need information about if now visual composer is something we must buy or if it's included. I think there's a lot of questions about this and this deserve a little effort from your side to communicate these changes in a clear way.
I'm not a developer or IT guy but I have been working with WP themes since 2006 and usually deal with with tech info but this is update is not the case.
I'm sorry if this seems not very kind but this update is taking to much time to be done and I think the people is quite lost...
I believe that the problems I'm having are due to the theme being installed on a multisite. The issues were not present in another site which is just a plain vanilla WP.
If anyone has had issues with this update in relation to a Multisite install I think it might be helpful to post them into this thread?
Could you please try renaming the "js_composer_salient" plugin folder to "js_composer" via FTP and check .
@Marc We were given a deadline to update to VC or get the theme off Themeforest which is the reason we could not test it thoroughly . Also everything had to be re-written from scratch causing these bugs.
Hey Ville,
ThemeNectar Support Team
Hi Tahir,
Thanks for the quick response. I updated to 5.5.3 but the problem is still there. If I deactivate the visual composer plugin everything works dandy (of course my site looks like a**) but I don't get any error messages in the back end.
Cheers
Ville
I think update to this version is not clear and a deeper step by step information is needed urgently.
First of all we need information about if now visual composer is something we must buy or if it's included. I think there's a lot of questions about this and this deserve a little effort from your side to communicate these changes in a clear way.
I'm not a developer or IT guy but I have been working with WP themes since 2006 and usually deal with with tech info but this is update is not the case.
I'm sorry if this seems not very kind but this update is taking to much time to be done and I think the people is quite lost...
Thanks
Back on to topic:
I believe that the problems I'm having are due to the theme being installed on a multisite. The issues were not present in another site which is just a plain vanilla WP.
If anyone has had issues with this update in relation to a Multisite install I think it might be helpful to post them into this thread?
Hey Ville!
Could you please try renaming the "js_composer_salient" plugin folder to "js_composer" via FTP and check .
@Marc We were given a deadline to update to VC or get the theme off Themeforest which is the reason we could not test it thoroughly . Also everything had to be re-written from scratch causing these bugs.
Thanks
ThemeNectar Support Team
Hi Tahir,
Boom! That solved it.
Thanks a bunch!
-Ville