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].
First: Thanks a lot for your work!
I am working on a site using your PageBuilder. Everythings is fine but the hero widget.
When I create a hero widget with picture, it shows correctly on my site page.
BUT: when I try to edit this widget in PageBuilder, it doesn´t show the image.
There is just the waiting symbol turning…
And the layout section on the right side shows only the padding button.
I tried with different sites and pictures. The predefined hero widgets don´t work also.
Any help would be greatly appreciated.
Best Regards
rd161
Hi Rd161,
Do you currently have Wordfence installed?
If you do:
This is a WordFence issue. The issue 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 me know if this helps.
If you don’t:
This is very likely a plugin conflict. Could you please try a plugin conflict test? 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.
Hi Alex,
thank you so much for your help!!
It was indeed a WordFence problem. I am not an expert in WordPress, so I didn´t think about WordFence as beeing so restrictive.
I did whitelist my own traffic as you said and now erything is fine.
Thanks again, it is great to have such a good support!
Best Regards!!