Support » Plugin: SiteOrigin Widgets Bundle » Beaver Builder 2.2.3.3 compatibility

  • Resolved Krea’Lab

    (@krealab)


    Hi

    I have an issue with the compatibility of Beaver Builder and your plugin. When I edit a page with Beaver Builder I can’t use the modules in this plugin and an ajax error is triggered.

    I have deactivate all the plugins in my website and the plugin who made this error is SiteOrigin Widgets Bundle.

    I tried to debug this error and I figure out that the error is in the file so-widgets-bundle.php in the function enqueue_registered_widgets_scripts() (line 809) and when I comment the lines 818 and 826 the error is gone.

    WordPress version: 5.2.2
    Beaver Builder version: 2.2.3.3
    SiteOrigin Widgets Bundle version: 1.15.7

    Is this error will be resolve quickly ?

    Best regards

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Andrew Misplon

    (@misplon)

    Hi, thanks for reaching out.

    At first glance, I can’t recreate this issue. The current version of Beaver Builder is 2.2.2.5. Perhaps try upgrading and see if the issue persists.

    Sorry I haven’t tell you that I am using the pro version of Beaver Builder which his current version is 2.2.3.3

    Plugin Author Andrew Misplon

    (@misplon)

    Thanks, and to confirm, the issue persists if you deactivate all other plugins and only have Beaver Builder and the SiteOrigin Widgets Bundle activated?

    Yes the error is only triggered when your plugin and Beaver Builder Pro are activated.

    Plugin Author Andrew Misplon

    (@misplon)

    Thanks. I’m unable to replicate the issue using 2.2.3.3. Is there a particular module that you’re adding that’s causing the problem?

    Have you tested with all plugins deactivated except for BB and the Widgets Bundle and at the same time activated a default theme like Twenty Nineteen?

    Please, send us the error you’re seeing in the JavaScript console.

    Using Your Browser to Diagnose JavaScript Errors

    I re-run some test this morning and I figured out that my server cache was too strong and the extension who triggered this error wasn’t yours but another.

    Sorry about the disturbing.

    Best regards.

    Plugin Author Andrew Misplon

    (@misplon)

    Hi, thanks for letting us know. We’re glad to hear you’ve made progress and located the issue.

    All the best 🙂

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.