Home>Support>Conflict with other plugins

Conflict with other plugins

Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].

Page Builder by SiteOrigin is a very useful and well designed plugin. It is a must for every WordPress editor. BUT:
It conflicts with so many other plugins and causes them to stop functioning properly on the page/post editor. On my site for example, Site builder conflicts with 3 other plugins!
Revolution Slider, WHMpress and Fruitful plugins
They have “shortcode creators” on page/post editors and it disappears when Page Builder plugin is active. For WHMpress and Fruitful that is a must to use shortcode creators. Otherwise you can not work with them.
I use SinglePage Pro theme and it has a shortcode creator which stopped working too!
In the image below, the yellow marked shortcode creators either disappear or stop working when Page Builder plugin is activated:

Is there any way to solve this problem?

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 8 years, 11 months ago Andrew Misplon
    Hi, I Work Here

    Hi Technonik

    Thanks for reaching out, we appreciate your support and the time involved in reporting these challenges. Running into three conflicts on one site like this is really unlucky, sorry for the hassles caused. Unfortunately, there is no quick, short term solution we can offer. I’ll certainly log the plugin conflicts you’ve reported for our developers to attend to. That said, we’re a small team so it would also be helpful if you reached out to the respective authors. Page Builder has over a million active installs at the moment so there is definitely an incentive there for the respective developers to make their products compatible with Page Builder. The fixes required to sort out conflicts like this don’t necessarily have to come from Page Builder, quite often a fix can be or needs to be carried out from within the conflicting plugin.

    Phew, so not really any good news above. Wish I had more. We’re working super hard to ensure conflicts like this don’t occur. If you feel up for contacting the other developers concerned, that’ll be helpful.

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.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More