Best slots to play online for real money philippines gcash.Claim Your Free 999 Pesos Bonus Today

Beaver Builder Lite conflict with SiteOrigin Widgets Bundle

clarevanessa — Wed, 13 Sep 2023 06:00:47 +0000

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.

Always Great

DB — Fri, 14 Apr 2023 14:53:12 +0000

I’ve been using SiteOrigin for 5 years now. Not officially at the beginning with SiteOrigin as my theme had a forked version of it, but I easily moved over to the official one, this one within a year later or so later. Anyway, been using Page Builder by SiteOrigin, SiteOrigin Widgets Bundle, and of course SiteOrigin Premium with 0 issues, and just all work with Classic and TinyMCE.

It’s my permanent building structure. So long as they permanently keep supporting Classic Editor / Classic Widgets

Ad units are not disabled

Nikonn — Thu, 07 Nov 2019 16:45:43 +0000

Hello. Testing your plugin on a test site and faced a problem, do not disable ad units on pages created with the plugin SiteOrigin Widgets Bundle. On ordinary pages created with a simple visual editor – unnecessary ad units are disabled. Can you recommend something to solve this problem? Thanks.

Your plugin breaks SITEORIGIN WIDGETS BUNDLE

jodani — Sat, 11 May 2019 12:23:00 +0000

If I have your plugin activated, then when I edit a page (using the SiteOrigin Widgets Bundle editor) – then the page will not render properly.

When I deactivate your plugin – then the editor works properly.

can you please fix this.

SiteOrigin Widgets Bundle install problem

hparali — Wed, 27 Mar 2019 11:10:28 +0000

Hello,
I am trying to install SiteOrigin Widgets Bundle on wordpress but everytime it gives error.

nstallation failed: 500 – Internal server error. Server Error 500 – Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed.

The website very slow

bpeter77 — Mon, 19 Nov 2018 09:23:41 +0000

Hi,
the website has a 20+ second time to load.
I inactivated all plugins and slow come back when activated I plugin the Vestige Core plugin or the SiteOrigin Widgets Bundle plugin.

Please help,

thanks

Contact form checkbox not showing

lauratraveler — Mon, 26 Mar 2018 19:11:19 +0000

Hi, I’m trying to use a checkbox for the privacy policy but the checkbox is not showing, so the user has no place where to click and the privacy policy cannot be made into a link via normal HTML. Could you please help? Thanks!

Elementor editor / SOWB Google maps widget error

Micemade — Tue, 28 Nov 2017 13:26:31 +0000

Hi,
great, great plugin – I’m using it with WP Widgets, SO Page builder, Elementor …
But, I found one (smallish) conflict when using it with Elementor – when on Elementor preview / editor page, there’s an error in Console:

Google Maps API error: MissingKeyMapError https://developers.google.com/maps/documentation/javascript/error-messages#missing-key-map-error – js-map.min.js?ver=1.11.2:1

The “js-map.min.js” is loaded from .. /wp-content/plugins/so-widgets-bundle/widgets/google-map/js/

It’s not appearing on frontend, and error doesn’t stop other JS execution, so it’s not big issue for me, but it might product errors in future (?) … Just something to check out …

Best regards.

Problem with Page Builder Version: 2.5.15 Social Widget

VVS Nair — Tue, 21 Nov 2017 12:50:55 +0000

Hi,

I have a curious problem after upgrading to Page Builder Version: 2.5.15. today

Social Media Widget, via SiteOrigin Widgets Bundle, when used in the main content area is rendering Vertically !!
Social Media Widget, SiteOrigin Widgets Bundle, when used in the footer area is working perfectly.

I wonder if anyone else has this curious problem ?

I have disabled & enabled all plugins to see if there was a conflict …. evidently not

One more thing my site has become very slow after the upgrade to Page Builder Version: 2.5.15.

Any solutions and ideas to fix this issue would be very welcome

Thank you in advance

Vijai Vir Singh

This breaks WP Customizer

Frank Shrum — Sun, 10 Sep 2017 14:51:32 +0000

Customizer quit working so I deactivated all plugin to find what broke it. Black Studio TinyMCE Widget was the culprit… Leaving it deactivated I proceeded to reactivate everything except Black Studio TinyMCE Widget and it broke again so back to square 1.

I went and deactivated everything and started reactivating them alphabetically, i.e all A’s, then all B’s, then all C’s and so on…

I got to the “S’s” and it broke again. Deactivated the “S’s” and started reactivating them one at a time getting to SiteOrigin Widgets Bundle and they broke again. Deactivated that and then I reactivated SiteOrigin Widgets by CodeLights and it broke, again, so I deactivated it.

I proceeded to reactivate all the rest of the plugins and the site never broke again.

For what it’s worth from me, I believe Black Studio TinyMCE is the central issue that caused this problem with WP Customizer and causes the SiteOrigin plugins to break.

I had to quit using SiteOrigin’s editor widget to get my sit to stop breaking a few weeks ago until they got something fixed concerning Black Studio TinyMCE and now their plugin is broke and so is this plugin and both of them are throwing the exact same error, whatever this error might be.

Below is what I documented as I discovered this problem and sought to find what’s causing it.

Testing. Is this what’s breaking WP Customizer? Black Studio TinyMCE Widget

YEP!!! This is what is breaking WP Customizer… Black Studio TinyMCE Widget

Reactivated everything and found that another plugin’s breaking it the same way…

Here’s the plugin I found breaking it, now – SiteOrigin Widgets Bundle

Now this one breaks it – SiteOrigin Widgets by CodeLights

Ok here’s what I’ve found breaking the Customizer in WordPress:

Black Studio TinyMCE Widget, then SiteOrigin Widgets Bundle, and finally SiteOrigin Widgets by CodeLights

Hope y’all get this fixed, soon.

Shalom,
Frank Shrum