Known Beaver Builder Incompatibilities

Here’s a list of items that are currently incompatible with Beaver Builder. Some have workarounds listed, others have issues that we can’t fix on our end.

Plugins

1. Advanced Custom Fields (Extra Widget Fields only) – Any additional fields added to widgets using ACF will not show up in the Beaver Builder interface.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. Schema Creator by Raven – Currently coded to only work in wp-admin.
8. 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.
9. Varnish on Cloudways hosting – If you use Cloudways with a multisite setup, their Varnish configuration causes issues with saving Beaver Builder settings. Turning off Varnish fixes the issue.
10. 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' );
11. WP Log Viewer – At the time this plugin was tested for this incompatibility (with WordPress 5.0.3), it hadn’t been updated for two years.
    • When both this plugin and Beaver Builder are activated, then existing Beaver Builder layouts can be edited, but when you try to add a new page or click Edit to open an existing page in WordPress, you’ll see the following error: “The editor has encountered an unexpected error.”
    • If you enable Beaver Builder for Posts, you’ll see the same behavior.
12. 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.
13. WPFront Notification Bar – Issue was posted on their support forums with no reply.

---

Themes

1. Blox Theme
2. Cherry Framework
3. Icelander Theme
4. Kleo Theme
5. Tesseract Theme

---

Services

1. 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.
2. Form Stack – When using the Javascript Embed Script option, the issue comes in when you have Form Stack load jQuery or jQuery UI.
   • 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 and the “I don’t need jQuery UI” box when getting your Form Stack embed code.
3. 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. 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.

---

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.

---

Source: https://kb.wpbeaverbuilder.com/article/42-known-beaver-builder-incompatibilities