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. Software changes 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. Some have workarounds lislted, others have issues that we can't fix on our end. 

Plugins

Advanced Custom Fields (Extra Widget Fields only)

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

Async Javascript

This is reported by a user, who was in contact with the developer:

This plugin works with Beaver Builder if both of the following conditions are met:

  • jQuery is excluded 
  • wp-includes/js is added to the Async Javascript > Settings > Scripts Exclusion field. 

EmbedPress

This plugin - with the help of extensions - adds additional features to embeds.  These features do not load inside of the builder.

Form Maker Pro

When this plugin is active, the Beaver Builder editor 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 (unload) two of the scripts in this plugin when the Beaver Builder editor is active. Add the code below to the functions.php file in your child theme or in a plugin that you create yourself.

Google Maps Bank (Shortcodes only)

Shortcodes from this plugin break Beaver Builder because document.write is used to render them. Everything else about this plugin should be fine.

Jetpack (Gallery Widget and VideoPress)

The settings panel for Jetpack’s gallery widget doesn’t fully load in Beaver 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.

Safe SVG

The Safe SVG plugin breaks the image size dropdowns and always resets the image to thumbnail in Beaver Builder layouts.

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.

WP Job Manager

The WP Job Manager plugin is not compatible with Beaver Builder because it takes over the_content, which doesn't allow Beaver Builder to run.

However, you can solve the problem by adding the following line of code to the functions.php file in your child theme.

add_filter( 'the_job_description', 'FLBuilder::render_content' );

WPFront Notification Bar

Issue was 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.

WP Retina 2x Pro

Reported by a user in contact with the plugin developer, Beaver Builder works with WP Retina 2x Pro as of Version 5.4.1. Some earlier versions of this plugin conflicted with the Builder UI loading due to a fatal error.

Themes

Blox Theme

Blox Theme is a fork of Headway. In recent releases, it prevents smooth scrolling in Beaver Builder from working. Version 1.01 of the theme is known to be compatible with smooth scrolling.

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 Beaver Builder functions such as opening module settings.

Icelander Theme

Versions prior to 1.1.8 of the Icelander Theme are incompatible with Beaver Builder Version 2.1. Icelander Version 1.1.8 or higher is compatible.

Kleo Theme

The module/row settings windows are blank with this theme active. It appears to be caused by one script. To fix it, try adding the code below to your child theme's functions.php, or incorporate it into a plugin if you know how to create one.

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 Beaver Builder, such as GeneratePress.

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 Beaver Builder when it loads the same version of jQuery that is loaded by WordPress.

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

Google AMP

Google's Accelerated Mobile Pages (AMP) is an open source initiative to speed up mobile websites. It does not allow JavaScript except for the AMP Runtime and also has limits on HTML and CSS, so it's not compatible with Beaver Builder for pages. If you want to know more about Google AMP, here is a fairly thorough discussion from the viewpoint of Google AMP's impact on JavaScript.

However, Google AMP should work with posts, even if they have Themer layouts.

Code

document.write (JavaScript)

Anything that uses document.write will break the Beaver Builder interface, because Beaver 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.