While Wordfence is active, you can no longer edit the SiteOrigin Button.
SiteOrigin Button and Wordfence Conflict
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Wireb,
This issue will be fixed in the next version. In the meantime, there is a workaround. 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…)
Alex,
Thank you for your response and the greatest service you provide to the WordPress community.
Kind regards,
WireB
The problem of script conflict with Wordfence still exist using PB Version 2.4.8.
Hi Wireb,
It’s not a conflict as that implies there’s no workaround – which there is as highlighted above.
Wordfence is doing something it thinks is right, albeit in a somewhat strange manner. We’re working towards resolving this issue but for obvious reasons we cannot provide an eta.
Hi Alex,
Any update on this or continue as above?
Hi HammerOZ,
As above. This isn’t something that can really be avoided.
cheers
This same conflict still exist with Wordfense and SiteOrigin’s Button plugin. I created a thread at Wordfense describing the problem: https://wordpress.org/support/topic/plugin-conflict-with-site-button/#new-topic-0.
Regards,
wb
Hi wb
I’m not sure there is a solution from our end. Please, see the below brief thread on training Wordfence. Thanks.
Thread: Date appearing when trying to edit widgets in Page Builder