Turning Page Builder caching off fixed it for me. Thanks so much for putting this up here!
Thanks for trying that. Ideally, the caching setting needs to be enabled in the future. We’ll update this thread as soon as we’ve taken a closer look at the problem. Thanks again.
Does that help anyone here still experiencing issues?
Not me. Caching was already disabled. I upgraded to WP 4.9 and Page Builder 2.5.15. Enabling/disabling the Page Builder Cache doesn’t fix it on WP 4.9.
All plugins deactivated – no Page Builder Tab. Forgot to clear browser cache, sorry – but now I’m already back on WP 4.8.3 with the tab…
Plugin Contributor
alexgso
(@alexgso)
Hi Everyone,
If you’re still experiencing this issue, you’ve tried a plugin conflict test, disabling content cache and you’re still using the latest versions can you please try viewing a page builder powered page. When the tab doesn’t show up, could you please send me the contents of your console? Please refer to this guide on how to access your browser console.
Folks it’s a wordpress bug (42574) occuring because of bad locale-handling in mediaelement core-module.
Occurs only when using locale with suffix (“-formal”).
People work on it.
Not a problem of page builder plugin at all.
cheers
Plugin Contributor
alexgso
(@alexgso)
Hi orlandooo,
Thank you for pointing this out – we were about ready to start pulling our hair out! That makes a lot of sense and would explain why we can’t replicate this issue.
You can find the aforementioned ticket here.
Simple workaround until 4.9.1 release:
change BACKEND language to English (in admin profile settings)
cheers
Perfect. Great idea. That’s a really quick and simple fix, also short term, can revert as soon as 4.9.1 is out. Thanks for your help.
change BACKEND language to English (in admin profile settings)
Works for me too. 🙂 Thanks!
Is it safe to upgrade to WP 4.9.1 now?
Plugin Contributor
alexgso
(@alexgso)
Hi augschburger,
Yes. WordPress has resolved the previously mentioned language issue in WordPress 4.9.1 so it’s safe to update. As always though, be sure to do a backup.
As WordPress has resolved this issue I’m going to mark this thread as resolved.
