Hi Dylan,

Do you have a public URL where we can take a look at what’s going on? If you need to keep this URL private from other users, just select “Private Reply” on the bottom right of the comment box.

Hi Dylan,

Would it be possible for you to send me an export for this widget? To do this open up the page with the widget and click layout. Then click import / export and then click download. Please upload the export to a 3rd party file hosting site such as teknik.io.

Preface: Please note that the following CSS will only work for Dylan.

To resolve this issue via CSS please add the following CSS to WP AdminAppearanceCustom CSS:

#panel-4-1-0-0 .so-widget-sow-button {
	display: block;

}

You might also need to install the SiteOrigin CSS Editor.

Hi Dylan,

Do you happen to have WordFence enabled? If you do, it’s likely WordFence preventing the export. 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…).

Hi Dylan,

Thank you for that. With the help of that layout I’ve managed to find the cause of this issue and it’ll be fixed in a future version.