Title: Plugin clash with "Page Builder"
Last modified: August 21, 2016

---

# Plugin clash with "Page Builder"

 *  Resolved [smokeys_13](https://wordpress.org/support/users/smokeys_13/)
 * (@smokeys_13)
 * [13 years ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/)
 * I am using the SiteOrigin Panels (“Page Builder”) plugin v1.2, and when I try
   to use this plugin in one of the panels, the TinyMCE editor doesn’t seem to load
   properly (if at all). It works fine under Appearance -> Widgets of course, but
   the form when editing within the page builder is failing.
 * I tried to see if I just needed to ensure an ID wrapper or something that’s different
   between the two circumstances, as there’s no JS error to point me to anything
   in particular, but have got nowhere so far.
 * Any help you can provide on the matter would be brilliant.
 * [http://wordpress.org/extend/plugins/black-studio-tinymce-widget/](http://wordpress.org/extend/plugins/black-studio-tinymce-widget/)

Viewing 13 replies - 1 through 13 (of 13 total)

 *  Plugin Author [Marco Chiesi](https://wordpress.org/support/users/marcochiesi/)
 * (@marcochiesi)
 * [13 years ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782173)
 * Hello,
    it looks like both Black Studio TinyMCE Widget and SiteOrigin Panels 
   use a lot of javascript code to render the widget forms. Unfortunately the way
   SiteOrigin Panels uses to to render the widgets is different from the one used
   natively by WordPress in widgets administration, hence the missing visual editor.
   However it should be possible to workaround this behavior and let it work with
   Page Builder too, even if it may be not so simple. I will look into this and 
   I will let you know in the next few days.
 *  Thread Starter [smokeys_13](https://wordpress.org/support/users/smokeys_13/)
 * (@smokeys_13)
 * [13 years ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782175)
 * Hi, thanks for your reply.
    Yea I looked at adding the .widget-inside container
   and altering your JS to work with .parent().parent() instead of .closest() – 
   the widget also needed to check $pagenow being “post.php” to set $load_editor
   to true. I got it closer to working, but not close enough. If you know what to
   be looking for/what needs to be changed I can have a look myself as well if you
   want.
 *  [Greg – SiteOrigin](https://wordpress.org/support/users/gpriday/)
 * (@gpriday)
 * [13 years ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782176)
 * Unfortunately I haven’t found a good way to make Page Builder compatible with
   all widgets. Marco, I’ll take a look on my side and see if I can get our plugins
   working together.
 *  Thread Starter [smokeys_13](https://wordpress.org/support/users/smokeys_13/)
 * (@smokeys_13)
 * [13 years ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782189)
 * Hi guys, don’t want to be too pushy but this issue is holding back a live job
   at the moment – is there any idea of when this could be sorted out by? I don’t
   really want to find alternates and re-code my widgets etc, but I might have to
   if it’s going to be too long for my client. It’ll still end up being used in 
   another project if it gets sorted, so don’t worry about it going to waste, but
   the active project that this is for at the moment is already past it’s original
   end date.
 * Any updates would be great! Thanks.
 *  Plugin Author [Marco Chiesi](https://wordpress.org/support/users/marcochiesi/)
 * (@marcochiesi)
 * [13 years ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782192)
 * Hi guys,
    I am actually working on this issue. In my current development version
   the two plugins may live together, but there are still some glitches that I have
   to fix. I plan to release a new stable version in the next few days.
 * [@greg](https://wordpress.org/support/users/greg/): Thanks, I appreciate that.
   I think one of the main reason for the compatibility issues may be the presence
   of duplicate IDs in the DOM in widget forms inside SiteOrigin panels. If you 
   create two panels based on the same widget they share the same IDs, and this 
   can be a problem if there’s some javascript code acting on that form (like in
   this case). Moreover it looks like there are duplicate IDs even with a single
   widget instance because there are 2 copies of the widget form in the DOM (one
   hidden in the panel and one in the dialog). I don’t know if there’s an easy solution
   to avoid duplicate IDs. In the meantime I am using some dirty trick to workaround
   it, by dynamically change the IDs.
 *  [Greg – SiteOrigin](https://wordpress.org/support/users/gpriday/)
 * (@gpriday)
 * [13 years ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782201)
 * I’ve managed to sort out a few of the conflicts with the WYSIWYG widget on my
   side. Thanks for the heads up on the conflicting IDs [@marcochiesi](https://wordpress.org/support/users/marcochiesi/),
   I’ve managed to sort that out in my dev version.
 * Would it be possible for you to email me your unminified JS source? I think I
   could make a lot of progress if I had access to that.
 * [greg@siteorigin.com](https://wordpress.org/support/topic/plugin-clash-with-page-builder/greg@siteorigin.com?output_format=md)
 *  Plugin Author [Marco Chiesi](https://wordpress.org/support/users/marcochiesi/)
 * (@marcochiesi)
 * [13 years ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782205)
 * Hi Greg, I’ve sent you my current development version (with unminified js), which
   works fine with the latest stable version of Page Builder.
    Please check your
   e-mail. Thanks for your cooperation.
 *  Thread Starter [smokeys_13](https://wordpress.org/support/users/smokeys_13/)
 * (@smokeys_13)
 * [13 years ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782210)
 * Sorry, but is there any chance of getting your development versions so I can 
   work towards getting our site finalised for our client? I appreciate that they
   are only dev versions at the moment, but as long as it’s working I should be 
   able to make any alterations needed to clean bits up for giving them a demo.
 *  Plugin Author [Marco Chiesi](https://wordpress.org/support/users/marcochiesi/)
 * (@marcochiesi)
 * [13 years ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782211)
 * Hi smokeys_13,
    sure, I can send you my current dev version. But consider that
   it may be quite different from the one that will be released, ’cause Greg is 
   working on it. Just tell me your email address.
 *  [Greg – SiteOrigin](https://wordpress.org/support/users/gpriday/)
 * (@gpriday)
 * [13 years ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782212)
 * As far as I can tell, everything will be forward compatible, my changes to Marco’s
   code have been fairly minor. As far as I can tell, there shouldn’t be any issue
   with you using the dev version, then updating to 1.2.1 when it’s available.
 *  Thread Starter [smokeys_13](https://wordpress.org/support/users/smokeys_13/)
 * (@smokeys_13)
 * [13 years ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782213)
 * Cheers guys, if it can be sent to [matt@squarehalo.co.uk](https://wordpress.org/support/topic/plugin-clash-with-page-builder/matt@squarehalo.co.uk?output_format=md)
   that’d be great.
 *  [FreelanceCreatief](https://wordpress.org/support/users/jaspergrafisch/)
 * (@jaspergrafisch)
 * [12 years, 12 months ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782222)
 * Could you send it to me (nazjas@home.nl) also please?
    Big thanx!
 *  Plugin Author [Marco Chiesi](https://wordpress.org/support/users/marcochiesi/)
 * (@marcochiesi)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782226)
 * Update: after spending some time together with Greg (the author of Page Builder)
   all the compatibility code is now included in the latest version of Page Builder,
   so there’s no more need for our dev version. Please update Page Builder and everything
   should work fine.
    If you’re still having issues, feel free to start a new topic.

Viewing 13 replies - 1 through 13 (of 13 total)

The topic ‘Plugin clash with "Page Builder"’ is closed to new replies.

 * ![](https://ps.w.org/black-studio-tinymce-widget/assets/icon.svg?rev=2627604)
 * [Black Studio TinyMCE Widget](https://wordpress.org/plugins/black-studio-tinymce-widget/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/black-studio-tinymce-widget/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/black-studio-tinymce-widget/)
 * [Active Topics](https://wordpress.org/support/plugin/black-studio-tinymce-widget/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/black-studio-tinymce-widget/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/black-studio-tinymce-widget/reviews/)

## Tags

 * [siteorigin](https://wordpress.org/support/topic-tag/siteorigin/)

 * 13 replies
 * 4 participants
 * Last reply from: [Marco Chiesi](https://wordpress.org/support/users/marcochiesi/)
 * Last activity: [12 years, 11 months ago](https://wordpress.org/support/topic/plugin-clash-with-page-builder/#post-3782226)
 * Status: resolved