Back last fall, I think I did a little hack of the plugin files (intending to come back to fix but didn’t get back–changing the path to uploaded png’s which were secured), which were of course, overwritten by the next update. I’m still showing insecure content warnings (see attached file) for this page: https://ncncucc.org/churches/
They look to be the image files for the map markers. Any idea how I can force the the plugin to use a more relative path without having to remember to re-hack every time?
When we changed our style sheet for Google fonts to deal with insecure content, we simply removed the “http://”. Maybe in the plugin files, you could change: “http://ncncucc.org/wp-content/plugins/store-locator-le/images/icons/bulb_azure.png” to “ncncucc.org/wp-content/plugins/store-locator-le/images/icons/bulb_azure.png”? (I know it’s more complicated than that, since the domain/blogname has to be dynamically generated.)