Home>Support>Woocommerce local pickup plus and SiteOrigin Widgets Bundle conflict

Woocommerce local pickup plus and SiteOrigin Widgets Bundle conflict

Hi there,

when using both plugins there is a display issue on the checkout page.

The Woocommerce local pickup plus plugin pulls the front (home) page in full into the areas were the pickup address is displayed.

When I disable SiteOrigin Widgets Bundle it does not happen.

Is there a way I can disable the widgets bundle plugin just for the Checkout page? Or just have it active on the front page only?

Many thanks
AM

This is a free community support forum. Replies are not guaranteed. If you need professional email support, please purchase a SiteOrigin Premium license.

  1. 8 days, 11 hours ago Alex S Hi, I Work Here

    Hi Alex,

    Unfortunately, it’s not possible to disable a plugin on one specific page. I’m unsure how it’s affecting this plugin however as it doesn’t really do much unless the plugin is being used on the current page (or you’re in the admin section).

    Do you have a public URL where we can take a look at this issue so I can get a better area of the resulting issue? Also, to confirm, does this issue occur if only SiteOrigin Widgets Bundle, WooCommerce, WooCoomerce Local Pick Up and if you have it installed, SiteOrigin Page Builder, are active? What about with a default WordPress theme?

  2. 8 days, 8 hours ago Alex Moss

    Hi there,

    thanks very much for the reply. Please visit:

    http://officialmerchandise.co.za/checkout/

    You will need to select an item to purchase first and then choose the option to pick up the item from our shop once on the checkout page

    After switching off every plugin, the only one that stopped the front page from appearing inside the pickup location area was the widgets bundle.

    This happens in the storefront theme as well as the twenty seventeen theme.

    Many thanks

  3. 8 days, 6 hours ago Alex S Hi, I Work Here

    Hi Alex,

    Oddly, I didn’t see any issues although I suspect that’s due to being in Australia rather than South Africa. I’m going to forward this thread to Andrew to see if he can replicate this issue.

  4. 8 days, 5 hours ago Alex Moss

    Sorry, yes you need to put your address in as being in South Africa.

    Do you need me to provide you with a test address to use?

    Many thanks for the help so far!!

  5. 8 days, 2 hours ago Alex S Hi, I Work Here

    Hi Alex,

    Andrew was able to replicate this (he’s based in Cape Town). He said this may be a page builder related issue as it reminded him of a similar issue we had with a third party plugin hooking into the_content in a specific manner. To clarify, does this issue occur if SiteOrigin Page Builder is disabled?

  6. 8 days, 1 hour ago Alex Moss

    Hi Alex

    I have just double checked to make sure.

    I disabled SiteOrigin Page Builder plugin and the issue did not occur.

    I think I might have suggested earlier that the issue was with the
    SiteOrigin Widget plugin! Apologies.

  7. 7 days, 8 hours ago Alex S Hi, I Work Here

    Hi Alex,

    Unfortunately, this suggests this is an issue with how the other plugin is handling the output of the data. Would it be possible to report this issue to the other plugin developers? I would include a link to this thread and this thread as Andrew suspects the issue is related.

  8. 7 days, 8 hours ago Alex Moss

    Hi Alex,

    they told me to speak to you!

    No worries. I will bounce it back to them and see what they say.

    Thanks for the help!

  9. 7 days, 8 hours ago Alex S Hi, I Work Here

    Hi Alex,

    Ah. In that case please send them a link to that thread and mention that we think the solution outlined in that thread will resolve this issue. This issue isn’t something we can reliably apply on our end.

  10. 7 days, 8 hours ago Alex Moss

    Ok. Many thanks.

Please log in to post on our forums. Signing up is free.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More