Home>Support>Bug Report: Conflict with Beaver Builder Standard Plugin and Pods Widget

Bug Report: Conflict with Beaver Builder Standard Plugin and Pods Widget

I have a workaround to this issue, but I thought I should report the problem to SiteOrigin, so that it can be addressed in a future release…

With SiteOrigin Widgets Bundle activated, I cannot save changes in “WordPress Widgets > Pods List Items” in Beaver Builder. If you add Pods List Items to your page using Beaver Builder, with SO Widget Bundle activated, you can make changes, but they won’t be saved; only the default settings will be saved.

When it happened, I contacted Beaver Builder support and they told me to deactivate the SiteOrigin plugin. I was then able to make and save the changes. I re-activated SiteOrigins afterwards so that we didn’t lose those features on our website (https://www.balanceanddizziness.org).

Beaver Builder said you could test this with their Lite version and Pods is a free plugin, as far as I remember. If you have any questions, I would be happy to assist and I’m sure Beaver Builder support and even Pods support would also be helpful. No one wants plugin conflicts!

Thank you!

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

  1. 6 years, 8 months ago Alex S
    Hi, I Work Here

    Hi Andrea,

    I’ve run a few tests and this issue is caused by this line. If there are no dependencies, it works without issue. I’m not too sure why this is happening but I suspect Beaver Builder changed how they handle assets in the most recent major update and this is a sign of that issue. I tried Beaver Builder back to 1.11 (the last version before 2) to see if that helped and it doesn’t appear to have worked so that rules that thought out (the one about being a change in how they handle assets).

    I’ve forwarded this thread to our lead to our developer to see if he has any ideas.

  2. 6 years, 8 months ago Andrea Wilson

    Thank you, Alex, I really appreciate the feedback. And I know BB would be happy to talk to you about the issue. At least I have a workaround, but since I only do this once a year, I’ll probably have forgotten by next year… hopefully, it will be fixed by then and I won’t have to puzzle over it again! :)

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