I need help on this issue am having difficulties tracking down root cause. My site is not rendering secure even though I have tried to make it that way. I get indicators that it has some insecure images and mixed content. The insecure image or one of them would seem to be a background image png which I am having trouble tracking down and the mixed content is also difficult to track down. Mixed content would be http mixed in with https. I have found this code on the source code of my home pg and I am suspect that it may be one of the problems. I think it is java code and I do not know what it is associated with on the pg. copying and pasting lines 30 and 31:
<script type="application/ld+json">[{"@context":"http://schema.org/","@type":"Service"},{"@context":"http://schema.org/","@type":"Painting","provider":{"@type":"Person"}}]</script>
</head>
I have my pg link at the bottom of my posts so anyone can view the code I have posted is lines 30 and 31 of my home pg source code, if anyone knows about this could use some advice or pointing in right direction to resolve https security problems. Thank you.

I think for now, you can just change the http to https after export. I will report it, as it seems that this has been overlooked in build revisions.

Thank you Inger, I can easily add the s to the two places. I have had the same site for years and have been importing and exporting it through all of the incarnations of the software over the years and changing from the different basic building frames it is a wonder that there are not many many more problems. It has been a most chaotic road traveled to get to where it is now.

We know, Greg! We've been following your battle throughout some years!

I'm wondering whether schema.org have overlooked this themselves, or whether http:// is the right way to do it. Their examples at https://schema.org/docs/gs.html#microdata_how all show http://schema.org ....

Frank

I'd think the examples are old. Everywhere else on the pages they are using https.
I have reported it to the CC staff, but since they take weekends off, I don't expect to hear anything until tomorrow.

I fixed the two https items on the source code and still get the grey lock box with the yellow triangle reporting not secure. Further investigation I found multiple counts of http code in a java script folder mainly the two picturefill.js files, guess that that would be the background images that have been reported in the error reports for the security problems. All pgs on the site which are many that use that java script have the security problem. My two examples of bids pgs and the blog and form pgs register secure ande the slide show pages on my testimonials pg also register secure all of these do not use the java code. Guess that I will have to looki into the picturefill.js code files and see if that fixes the problem.

The SD prog. seems to be using only the picturefill.min.js. In my version of SD there are two instances of https and one http (to the w3.org). I don't think anything will break if you add an s, but keep a copy of the original, just in case.

I have lots of files in the js folder. went through all of them i could and found lots of http code minus the s. changed all that I found and saved and uploaded. Still getting not secure notification. Would be easy to miss some in all of that code. Guess i will put in trouble report tomorrow.

It would be interesting to know what test is giving the 'insecure' notification, suggesting 'insecure images and mixed content', and whether that test would indicate a problem regarding every web page including the http:// created by SD4's use of it when one includes structured data.

Frank