In doing a search I have seen this problem and done the suggested fixs:
– Disalbe all plugins
– Install the Twenty Fifteen thread
Neither of those did the trick.
I am hosted on DreamHost. Is this a memory issue perhaps? Any other ideas?
In doing a search I have seen this problem and done the suggested fixs:
– Disalbe all plugins
– Install the Twenty Fifteen thread
Neither of those did the trick.
I am hosted on DreamHost. Is this a memory issue perhaps? Any other ideas?
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Gene,
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 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,
– I don’t have Word Fence installed.
– All plugins except Site Origin are disabled
– Cache has been cleared
– I tried increasing memory to 64MB (I was not receiving out of memory messages)
This is hosted on Dream Host and since I have other domains I tried them and they work fine with site origin.
The site is on a staging directory but the same problem exists within the root instance of WP that hosts a temporary site.
For grins I disabled all of the plugins on the other instance of WP within the root directory but still not working.
Kind of at a loss. Thinking I should just rebuild the whole directory from scratch.
This is a private message.
This is a private message.
Hi Gene,
Theme Trust runs a fork (a version based on our code but not actively developed by us) of SiteOrigin Page Builder and I suspect this is an issue with the version they forked. Would it be possible for you to uninstall their version of the plugin and install ours instead?
Be sure to do a backup before doing this.
That fixed it. SMH, all that time for a simple fix. I was convinced it was a corrupted install of WP.
Thanks for the help
have a great weekend,
GK
Hi Genem
Bad luck mate. :( You too! :)