Beaver Builder Lite conflict with SiteOrigin Widgets Bundle

  • We have just encountered an issue editing pages with Beaver Builder Plugin (Lite Version) 2.7.2.1, where we get the error message ‘Beaver Builder has detected a plugin conflict that is preventing the page from saving’, and the entire top taskbar containing the discard / save draft / publish buttons is blurred out so changes to the page can’t be saved or published.

    As instructed in the knowledge base on Beaver Builder’s website, we deactivated all plugins except Beaver Builder and then reactivated all other plugins one by one and test-edited a page with Beaver Builder each time we reactivated a plugin to see if/when the issue recurred. We found Beaver Builder worked perfectly with all plugins reactivated except the plugin SiteOrigin Widgets Bundle Version 1.54.0 so this seems to be the cause of the issue we are having and we have left it deactivated for the time being. But we would like to be able to reactivate this plugin again as we have several widgets that are located in the footer of the website using this (and we want to avoid having to recreate them in another plugin or within a new theme footer). Beaver Builder was editing fine until recently, so I’m guessing a recent update of either Beaver Builder or SiteOrigin has caused the conflict.

    Below is the error from within the Javascript console of my browser (Vivaldi):

    Uncaught TypeError: Cannot read properties of undefined (reading ‘nodeType’)
    at _saveSettingsComplete (fl-builder.js?ver=2.7.2.1:7107:26)
    at Object.success (fl-builder.js?ver=2.7.2.1:10301:15)
    at fire (jquery.js?ver=3.7.0:3213:31)
    at Object.fireWith as resolveWith
    at done (jquery.js?ver=3.7.0:9617:14)
    at XMLHttpRequest. (jquery.js?ver=3.7.0:9878:9)

    and this is the URL provided by Beaver Builder’s Debug Mode:
    https://animal-communicator.com.au?fldebug=20c3e70752f592a19a282adf097075b8

    Any suggestions on a solution so we can continue using both plugins?

    Thanks.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Jamie

    (@codente)

    So far, I’m not able to replicate this issue. The issue occurs for you when Beaver Builder and SiteOrigin Widgets Bundle are the ONLY plugins active on the site?

    Also does it happen on just that page or every page on your site?

    Finally, does it happen with every module you are adding/editing or just a certain one or certain ones?

    • This reply was modified 1 year, 2 months ago by Jamie.
    • This reply was modified 1 year, 2 months ago by Jamie.
    Thread Starter clarevanessa

    (@clarevanessa)

    Hi Jamie,

    Thanks for your reply. At the time I started this topic, I had deactivated all plugins but reactivated them one by one until I encountered a conflict (to avoid the process being even more time-consuming!). So as per your question, I have now also tested deactivating all plugins except Beaver Builder Lite and SiteOrigin Widgets Bundle and in that state I can successfully edit and publish changes to multiple pages using Beaver Builder (and yes, the original error was occurring on more than one page of the site and using multiple modules – it wouldn’t save any changes).

    I had read similar topics before posting this, and noticed a previous solution noting potential conflict issues when using the Custom Fonts plugin along with the Astra theme (our site also uses both of these). To test if the Custom Fonts plugin was involved in the conflict, I activated it at the same time as Beaver Builder Lite and SiteOrigin Widgets Bundle (while all other plugins remained deactivated) and I again couldn’t edit any page with Beaver Builder. I then reactivated all other plugins except for Custom Fonts, and I could again edit pages with Beaver Builder. Alternatively, I reactivated all plugins except for Site Origin Widgets Bundle, and I could again edit pages with Beaver Builder.

    So to recap, I can edit with Beaver Builder when:
    – Beaver Builder Lite and Site Origin Widgets Bundle are the only plugins activated on the site;
    – Beaver Builder Lite and Custom Fonts are the only plugins activated on this site;
    – Beaver Builder Lite, Site Origin Widgets Bundle and all other plugins are activated, but Custom Fonts is deactivated;
    – Beaver Builder Lite, Custom Fonts and all other plugins are activated, but Site Origin Widgets Bundle is deactivated.

    As an extra note, we don’t have ‘Preload Fonts’ selected in the settings for Custom Fonts (as I noted was an issue in a previous similar topic).

    Also, just in case it is needed, I had disabled Beaver Builder’s Debug mode when testing the various scenarios above, but have reactivated it again – the new URL is: https://animal-communicator.com.au?fldebug=e34d20e32d56989b93a8182f24e6a5b3.

    Look forward to hearing any further thoughts / suggestions and thanks in advance for your help!

    • This reply was modified 1 year, 2 months ago by clarevanessa.
    • This reply was modified 1 year, 2 months ago by clarevanessa.
    Plugin Contributor Jamie

    (@codente)

    This might be a tricky one but it doesn’t look like the issue is on BB’s end.

    When those two plugins are active, html from the Custom Fonts plugin gets injected into our AJAX response.

    That doesn’t happen with just the Custom Fonts plugin active so it’s definitely an interaction between the Custom Fonts plugin and the SiteOrigin Widgets Bundle plugin. We can report it to the Custom Fonts plugin team and see if this is something that can get resolved but when there’s 3 plugins involved, it’s always more complex.

    Thread Starter clarevanessa

    (@clarevanessa)

    I can appreciate this is a difficult one to work out, and that would be great if you could report it to Custom Fonts and see if they can work something out or to help anyone else who runs into this in future (for now, I think we will just have to delete either Site Origin Widgets Bundle or Custom Fonts in order to work around the conflict another way). Thanks for your help anyway, Jamie, very much appreciated ??

    Plugin Contributor Jamie

    (@codente)

    You’re welcome! Just a small update to say, I have reported it and I will keep you apprised here if I get any updates on the matter.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Beaver Builder Lite conflict with SiteOrigin Widgets Bundle’ is closed to new replies.