Known Page Builder incompatibilities
We try our very best to make Page 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 Page Builder.
Here's a list of items that are currently incompatible with Page Builder.
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.
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.
Incorrectly loads in jQuery causing a second version to be loaded which breaks many scripts on the page, including Beaver Builder scripts.
Currently coded to only work in wp-admin.
Issue posted on their support forums with no reply.
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.
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.
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.
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