Known Beaver Builder incompatibilities

We try our very best to make Beaver Builder compatible with everything you throw at it, but sometimes there’s nothing we can do. Things change rapidly, so if you want to give these plugins and themes a try anyway, let us know if the developer made them compatible with Beaver Builder.

Here's a list of items that are currently incompatible with Beaver Builder.

Plugins

Advanced Custom Fields (Extra Widget Fields only)

Any additional fields added to widgets using ACF will not show up in the builder interface.

Google Maps Bank (Shortcodes only)

Uses document.write to render shortcodes. Everything else about this plugin should be fine.

Form Maker Pro

When this plugin is active, the Page Builder UI does not fully load. This issue does not seem to affect the free version of this plugin.

The only solution we have found is to dequeue (not load) two of the scripts in this plugin when the Page Builder UI is active. Add the code below to the functions.php file in your child theme or in a plugin that you create yourself.

Jetpack (Gallery Widget and VideoPress)

The settings panel for Jetpack’s gallery widget doesn’t fully load in the builder because it is only coded to load in wp-admin/widgets.php and wp-admin/customizer.php. VideoPress calls admin-only code that breaks the& ;media uploader on the front-end.

Post video players, slideshow albums, photo galleries and music / podcast playlist

Incorrectly loads in jQuery causing a second version to be loaded which breaks many scripts on the page, including Beaver Builder scripts.

Schema Creator by Raven

Currently coded to only work in wp-admin.

Timber

Timber is a plugin that enables the use of twig, a templating engine that eliminates the WordPress loop and allows for simpler code when creating templates. Given their names, you'd think that "Timber" and "Twig" would be a perfect match for "Beaver Builder," but they're incompatible.

The problem is that Timber doesn’t use the_content, which is the basic WordPress loop. This causes an incompatibility between Timber and any other plugin that relies on the WordPress loop.

If your theme allows it, calling the_post(); in your page.php file above the Timber code will enable the loop and allow Beaver Builder to function correctly. Note that this doesn't work for every theme.

WPFront Notification Bar

Issue posted on their support forums with no reply.

WP-Optimize

In certain cases, this plugin can leave thousands of rows of orphaned post meta (bloating your database) because it has issues with deleting post meta for revisions. There is a ticket for this issue that you can follow on GitHub.

Yoast SEO (clean permalinks feature)

When the clean permalinks feature is enabled on the Yoast SEO settings Advanced tab, Page Builder will not load. For information about how to disable this feature, see the Yoast knowledge base.

Themes

Tesseract Theme

Tesseract appears to have dropped support for Beaver Builder and taken away the templates they were originally offering. As an alternative we recommend either the Beaver Builder Theme or any alternative theme known to integrate well with Page Builder, such as GeneratePress.

Cherry Framework

There are multiple incompatibilities, depending on the Cherry Framework theme being used. Of many issues, the one that cannot be fixed by Beaver Builder is a hardcoded script in header.php that interferes with Page Builder functions such as opening module settings.

Blox Theme

Blox Theme is a fork of Headway. In recent releases, smooth scrolling in Page Builder does not work. Version 1.01 of the theme is known to be compatible with smooth scrolling.

Kleo Theme

The module/row settings windows are blank with this theme active. It appears to be caused by one script. The code below would go in a child theme functions.php or a plugin if you know how to create one.

Services

CloudFlare’s Rocket Loader

This CloudFlare feature can interfere with Beaver Builder when building sites, but it’s fine to turn it on after a site is finished.

Form Stack

The issue comes in when you have Form Stack load jQuery. This conflicts with Page Builder because it is already loading the version of jQuery that comes with WordPress.

To avoid this issue, check the "I don't need jQuery" box when getting your Form Stack embed code.

Code

document.write (JavaScript)

Anything that uses document.write will break the Page Builder interface because Page Builder content is loaded via AJAX when you make updates. Calling document.write after the page loads will cause it to overwrite all of the page content with the content passed to document.write.