Customizer compromised

Resolved 4 replies pluginplugin-page-buildertechnical
kjellerupbiz
1 year ago · Last reply by Alex S 1 year ago

Hi

I have issues with the customizer whenever I install woocommerce and Site Origin Page Builder.

An image of how it looks, without woocommerce (same goes without Page Builder but with woocommerce):

Perfect

– and an image of how it looks with woocommerce and Page Builder: Not good

Any idea why?

It happens with themes: “Corp (child)” and “Vantage (child)” – the themes I prefer to work in.

Thanks in advance

Mick

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

Need fast email support? Get SiteOrigin Premium

Replies

4
  1. Alex S Staff 1 year, 1 month ago

    Hi Mick,

    Thanks for reaching out. I’ve run a few tests, and this issue occurs if something outputs HTML a little too early in the Customizer. It’s very easy to unintentionally cause so it could be caused by a few different things. Does this issue occur if only SiteOrigin plugins are active? This will allow us to rule out WooCommerce as being unrelated.

    Kind regards,
    Alex

  2. kjellerupbiz 1 year, 1 month ago

    Hi Alex

    Thanks for reply!

    I will test it today and deactivate plugins one by one to see ‘when’ it happens.
    Let you know as soon as it’s done J

  3. kjellerupbiz 1 year, 1 month ago

    Hi Alex

    I have been running through everything.
    The first plugin that causes the problem is:

    Disable bloat for WordPress & Woocommerce
    By Disable Bloat

    However, if ‘disable bloat’ still runs and I deactive woocommerce, same thing happens, so it isn’t just the ‘disable bloat’ that causes them commotion but Woocommerce too.
    Still: If I deactive the first one, I can have Woocommerce running without problems apparently – so I’ll be looking for another way to deactivate the bloat since I don’t like it at all J

  4. Alex S Staff 1 year, 1 month ago

    Hi Mick,

    Thanks for trying, and for running a plugin conflict test. Based on the name of the plugin, it’s likely that the plugin is adding something WC specific when it’s active and results in this issue. I recommend reporting this issue to the developer.

    Please feel free to open a new thread if anything else comes up.

    Kind regards,
    Alex

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