Hi Allison,

This is a warning being issued by your browser. Once you “Allow”, do you get this prompt on subsequent tries?

I found a forum post that may explain the issue better. 

Most likely you have “mixed content”. Visitors to sites protected by SSL expect (and deserve) security and protection. When a site doesn’t fully protect or secure all content, a browser will display a “mixed-content” warning. Mixed content occurs when a webpage containing a combination of both secure (HTTPS) and non-secure (HTTP) content is delivered over SSL to the browser. Non-secure mixed-content-error content can theoretically be read or modified by attackers, even though the parent page is served over HTTPS.

To fix this you would need to be able to identify the non secure content within the code of the site. Most common day browsers like Google Chrome and Mozilla Firefox have an ability to look at the code in a developer instance meaning its like debugger console built into the browser. In Google Chrome you would right click on the page that is displaying the warning and select “Inspect.” On Mozilla Firefox same idea but they call it “Inspect Element.” Once you have done this look for any “Mixed Content” warnings.

Let us know if this was helpful. 

Thanks for the super-quick reply.  I didn’t think it was related to the entire page because we don’t get the error on page load, only when clicking on the email field (opening new email window).  

If I change the email field’s metadata type from email to url in the skuid model, I also don’t get the error (but then, can’t get the email window to open properly).

There isn’t an option to “allow” since all the settings are already set to allow, the certificate is valid through 2019, etc.

Sorry, I thought the browser was giving you the option to change Notifications and Popups settings and defaulted to “Allow”.

Do you get an error message(s) in the developer console when you click the email address?

no, no entries in the developer console at all when clicking on the email.

I’ll keep checking on my end. Go ahead and share the browser you’re using and version of Skuid.

Let’s see if anyone on the community has experienced this issue. 

Thanks.  We’re on Chrome and just upgraded to the lastest Skuid update 11.2