If I ADD a button I can edit it. If I try to edit an existing button in the Page Builder, it just sits with a “loading” image and won’t load for me to edit. Using WP 4.5.1, Page Builder 2.4.6 & Widgets Bundle 1.5.11
Any ideas on why this happens?
Site Origin Button Not Loading
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Lockhart
Sorry to hear about the hassle. The perpetual loading icon is most often caused by a plugin conflict or a memory shortage issue. To check for a plugin conflict, please, see the steps outline below:
This sounds like it could be a plugin conflict issue. Can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.
After chatting with the guys at the office, it’s possible this is a WordFence issue, please see our steps below:
This is a WordFence issue. The issue with that plugin is that it’s initially very strict so things like the Learning Mode do definitely help in resolving issues like this one. However, if you want to “skip” the learning process and just use your widgets you can do so pretty easily. Go to the affected widget and open it up, don’t get “blocked” yet. Instead open up another tab on WP AdminWordFenceLive Traffic and filter it by blocked traffic. Then make an adjustment to your button widget and you’ll get blocked. Go back to the Wordfence tab and press the whitelist param from FireWall button. This is 100% safe as the contents of the field are not at all close to what would be required for an XSS attack. (it’s really quite odd it would even suggest such a thing…).
Let us know how that goes :)
That worked. Thanks.
Super :) Glad to hear that did the trick.
Will you be updating the plugin to correct for this? I ran into this too.