Has this issue been resolved for you? We just got the 2.4.1.1 update but are still running into the issue when adding regular modules like text and image.
It seems as though clearing the page builder cache has fixed this particular error for my team. I normally clear that out after every update but hadn’t had a chance yet.
For multi-site, only Super Admins have the unfiltered_html capability. On stand-a-lone installs, both Admins and Editors have it.
You can use a plugin to add the unfiltered_capability to other roles. Role manager plugins that are compatible with Multi-Site should allow this. There is also this Unfiltered MU – WordPress plugin | WordPress.org but it hasn’t been updated in a while so not sure if that still works.
Another option is to add the following to the child theme functions.php as it would give all roles the ability to add unfiltered_html just in Beaver Builder.
Seems like an odd thing to have to do, we’ve been using beaver builder for several years now and only just ran into this a couple of weeks ago. Wordpress disabled this functionality for most users because it was “rarely ever needed”.
This unfiltered_html permission could be very dangerous in the wrong hands, so please don’t give this permission to any users you do not trust. WordPress has disabled this permission for most users because they rarely need it.
No unfortunately, I used our User Role Editor plugin to grant unfiltered_html access to our site editor role but my team continues to run into issues saving regular modules unless they’re using my super admin access.
Basically when the editor is initialised, if the user has unfiltered_html via wp… or using the filter… the code that makes this popup is totally ignored and it would be impossible to see the popup.