I rolled wp back to the previous version.
Yep – same here.
Thanks for the link on how to roll it back!
Issue is primarily with Visual Composer. I believe they (TagDiv) are waiting on WPbakery to update VC before TagDiv can push an update with the new version.
Also useful to go READ the changes to WordPress for each major full dot update vs ‘patch update.’ Note all the changes to how images work. This means generally you may need to regenerate your thumbs for the new compression optimizations.
Always keep BACK-UP of your working site, before doing ANY major update to WP, so you can seamlessly ROLL BACK to prior version. Good time to plan for that as it’s a basic WP admin skill everybody running a website that is more than a blog should learn.
I no longer provide help/support around these parts, but popped in to see how the fur was flying before I even attempted my updates. Also checked the VC support forum where everybody freaking out.
ALSO be aware that WP sometimes have its own inherent bugs — but normally those should have been tested by major plugin devs (ahem WPBakery you froods!) with the RC1 and RC2 versions prior to WP releasing latest build today as stable version.
Anyway…. just some feedback as long time lurker here (2.5 years so far … ) 🙂
Roll back if you can. Try disabling VC if you can’t.
Also good time to make sure you disable auto-updates of WP core files, if you don’t already do that.
Hi
We’re sorry for all these inconveniences.
There is jQuery conflict and some of theme’s features are affected. We investigate this and will release an update in shortest time possible. Meanwhile you can add this line in tagdiv_theme.js file as a temporary fix: http://screencast.com/t/Ur4jw4L6Z8
jQuery("a[href*='#']").click(function(e) {
Thanks for your understanding!
Hi
Try to deactivate all plugins except Visual Composer, clear all caches and test again. If the problem persist deactivate lazy load animation from theme panel > template settings: http://screencast.com/t/y8CTxGuyMMu
Thanks!