Archives for January 2018

For a current project, I decided to use Beaver Builder for certain pages that the client can edit with a drag and drop editor. I ended up using Elementor Pro*.

However, many people use Beaver Builder and WooCommerce together. In this situation you’ve got WooCommerce pages that are core (required) and generated when you go through the installer. These pages have shortcodes in them and they are also specified in the WooCommerce settings. These pages also should be excluded from Beaver Builder so you don’t have to explain this concept to your client. So here’s how you remove the ability to use Beaver Builder on WooCommerce pages. If you look at the code, you can also see that once you get the id, you can also remove Beaver Builder from other pages.

* I am using Elementor Pro because Beaver Builder had bugs with a core js file that I needed, that being Fancybox 3 (a known bug they say is a problem with Fancybox), and it had other issues with ShortCake. Elementor (the free version) is pretty robust and it’s all there on Github, so I can usually find an answer or search the code there. Plus they respond fast with most feature requests and bug reports. With Beaver Builder I found it more difficult to find the answers. Incidentally, I didn’t dig too deep in the Fancybox 3 + Beaver Builder issue, but the issue does not happen with Elementor. I still have an issue with Shortcake inside Elementor, but I can remove the IU script with one of their hooks so it doesn’t bug out and it’s still usable.