Jamie

Since you’ve also submitted a ticket to our help desk, we are going to reply here for anyone else and then close this ticket so we don’t have to keep replying in two places.

The unsafe-eval requirement comes from the WordPress media library, which depends on Backbone.js and Underscore.js. This is a WordPress core dependency that applies whenever the media picker is used in the editor.

Since the editor is only ever accessed by logged-in administrators, you can scope unsafe-eval to editor URLs only like something like this in .htaccess:

<If "%{QUERY_STRING} =~ /fl_builder_ui/">
      Header always set Content-Security-Policy "default-src 'self' 'unsafe-inline' http: https: data:; script-src 'self' 'unsafe-inline' 'unsafe-eval' http: https: data:; style-src 'self' 'unsafe-inline' http: https: data:"
  </If>
  <Else>
      Header always set Content-Security-Policy "default-src 'self' 'unsafe-inline' http: https: data:; script-src 'self' 'unsafe-inline' http: https: data:; style-src 'self' 'unsafe-inline' http: https: data:"
  </Else>

• This reply was modified 1 week ago by Jamie.
• This reply was modified 1 week ago by Jamie.

Good news! A fix for this is in UABB Lite now and a fix for the Pro version of UABB is coming as well next week.

Our builder is affected by improper HTML such as unclosed elements like this because it prevents the necessary scripts for our product and even WordPress from loading in the footer.

We’re not able to tell you exactly what the problem is as that would require actually seeing the theme code.

You can look in your theme template files for the markup and see if there is a missing closing markup tag. You can take screenshots of your theme template files and we can try to help you locate the issue but the issue is not related to a problem with Beaver Builder from what we can tell.

What we’d recommend to confirm it’s a conflict as we suspect first, please attempt to disable all plugins (except Beaver Builder Lite), and use one of the default (Twenty*) themes. If the problem goes away, enable your theme again instead to see if the issue comes back. If it does, then you’ve confirmed the issue is with your theme. If the problem does not come back after re-enabling your theme, then you can activate your other plugins, one at a time, checking to see if the problem comes back after each activation.

If you can install plugins, you can install and activate “Health Check”: https://wordpress.org/plugins/health-check/
It will add some additional features under the menu item under Tools > Site Health.
On its troubleshooting tab, you can Enable Troubleshooting Mode. This will disable all plugins, switch to a standard WordPress theme (if available), allow you to turn your plugins on and off and switch between themes, without affecting normal visitors to your site. This allows you to test for various compatibility issues. You would enable Beaver Builder Lite in troubleshooting mode to test to see if it’s a plugin or theme compatibility issue.

There’s a more detailed description about how to use the Health Check plugin and its Troubleshooting Mode at https://make.wordpress.org/support/handbook/appendix/troubleshooting-using-the-health-check/

Were you editing an archive with the block editor at the time so using Full Site Editing?

Were you using any module blocks?

• This reply was modified 5 months, 3 weeks ago by Jamie.

You can view the source of that page and see that the markup ends without being properly closed. It looks to be a div with the class of “footer-copyright” that is unclosed.

https://validator.w3.org/nu/?doc=https%3A%2F%2Fswwoodcarvers.org%2Fmeetings%2F

• This reply was modified 5 months, 3 weeks ago by Jamie.

It was determined by the user that this CSS in the user’s theme was the cause as it targets all divs and all buttons.

a, i, span, div, input, select, textarea, article, section, input[type=button], input[type=submit], button {
-webkit-transition: all 0.3s ease-in-out;
-moz-transition: all 0.3s ease-in-out;
-ms-transition: all 0.3s ease-in-out;
-o-transition: all 0.3s ease-in-out;
transition: all 0.3s ease-in-out;
}

• This reply was modified 5 months, 4 weeks ago by Jamie.