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].
After editing the content in Site Origin Hero, I clicked update and the new content is visible on the front-end. BUT, when I try to go back-in to edit the Hero, I just see the spinning/loading wheel. So basically, I’m unable to access my Hero content in the backend. Please help!
Hi Dfcultures,
Do you currently have Wordfence installed?
If you do:
This is likely 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 Admin > WordFence > Live 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. 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.