This thread is over two years old and may be outdated. Please create a new thread if you need help, or email us if you have an active Premium license.

SiteOrigin Widget bundle conflict with Elementor plugin

Open 3 replies bug-reportpluginplugin-widgets-bundle
Pakpoom Tiwakornkit
9 years ago · Last reply by Pakpoom Tiwakornkit 9 years ago

Hi SiteOrigin support team,

After SiteOrigin Widget Bundle has released new version 1.8 which added supports for Elementor Page Builder, I tried building a simple widget(build on top of SiteOrigin Widget Bundle framework which I followed the guide here https://siteorigin.com/docs/widgets-bundle/getting-started/creating-a-widget/) and insert that one in Elementor page builder to check if SiteOrigin-based widget is fully compatible with Elementor Page Builder. Everything looks great at first, I can drag my SiteOrigin-based widget into Elementor and change my LESS variables in Elementor panel on the right.

The conflict happened after I tried duplicating an Elementor column or section containing my SiteOrigin-based widget and press “save”, the generated CSS file(compiled from LESS file) by SiteOrigin Widget Bundle framework was deleted immediately. This conflict causes my duplicated widget to not have CSS file to apply, on the other hand, my SiteOrigin-based widget is rendered without any CSS rules and 404 response of not-existing CSS file shows in console log.

the followings are my PHP, WordPress and plugins version.
– PHP 5.6.21
– WordPress 4.7.2
– SiteOrigin Widget Bundle 1.8
– Elementor 1.2.0

Thanks in advance.

Pakpoom

This is our free support forum. Replies can take several days.

Need fast email support? Get SiteOrigin Premium

Replies

3
  1. Greg Priday Staff 9 years, 22 days ago

    Thanks for reporting this issue Pakpoom. We’ll look into it and try come up with a fix.

  2. Greg Priday Staff 9 years, 22 days ago

    Hi Pakpoom

    We’ve had a look into this. At the moment it’s a bit of an edge case that might be quite difficult to fix. In the meantime, the workaround is to just save and refresh. Everything goes back to normal after this.

  3. Pakpoom Tiwakornkit 9 years, 22 days ago

    Hi Greg,

    Wowww thank you for your speedy response. I appreciate your hard work. Thank you for investing your time on looking into the issue :)

    The workaround you advised me — by saving and then refreshing in Elementor editor page — doesn’t work unfortunately and not-existing CSS file that should be applied to the custom SiteOrigin-based widget also causes the widget-styles issue in the front-end page(where the visitors view). I found that the only way to make SiteOrigin Widget Bundle framework recompile LESS file is to change any form field of SiteOrigin-based widget.

    I know it’s kind of hard to fix as Elementor team doesn’t consider making their plugin compatible with the competitors’ plugins like SiteOrigin, etc. Therefore SiteOrigin team and all volunteers on Github have to make the plugin compatible with Elementor from their side.

    The workaround I have done is to hide “Duplicate Button” in Elementor editor page — by hooking into “elementor/preview/enqueue_styles” action. If users can’t click “Duplicate Button”, the issue won’t occur LOL.

    Thanks

    Pakpoom

Replies on this thread are closed.

Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Have a different question or issue?

Start New Thread