webaware

G’day @maffi1986,

This plugin accommodates multiple markers through KML files. There are easier ways using other plugins, however, like this one:

https://wordpress.org/plugins/leaflet-maps-marker/

cheers,
Ross

G’day Amie,

Excellent. I’ll get this released when I get a chance, maybe tomorrow. You’ll be able to automatically update once it’s released. Thanks for your assistance testing this.

cheers,
Ross

The less work the plugin has to do to clean things up, the better. Ultimately, the aim is to not run the plugin! But if that’s not achievable, anything below Capture is good.

I’d only search / replace for your domain name to start with. You know that one is safe. Then check for things that still break, and individually fix those (e.g. images / videos from external sites).

Sorry, can’t help further with Google Ads. Best to speak to them.

cheers,
Ross

In case you haven’t already gone ahead and dropped Capture mode…

Would you like to try what will become the next version of the plugin? It now doesn’t capture whole pages in the admin, just cleans up errant scripts / stylesheets and dynamic image links.

https://www.dropbox.com/s/8ban14o77q5a9nv/ssl-insecure-content-fixer-2.3.1-dev.zip?dl=1

I reckon this should fix the problem. Please give it a go if you can.

cheers,
Ross

It’s possible for some ads to still load things incorrectly on http from an https website. If that happens, you should report the ad to Google Adsense for them to chase up the advertiser.

Generally, if you’ve updated your Adsense code to be https-compliant, it should be no problem though. Check that you’re using the right code:

https://support.google.com/adsense/answer/10528

I’d advise taking a backup(!) and updating all internal links to https. You’ll get better use of browser caches, and if your server supports HTTP/2 (or you use a transparent CDN like Cloudflare) then it’ll be faster too.

I’ve never used Velvet Blues Update URLs — it looks good though. I have used Better Search Replace, so I can verify that it works well. Either would do the job. Just remember to backup the database first!

cheers,
Ross

It sounds like it might be tricky to track down what’s happening here. Perhaps a better approach would be to resolve the reasons why you need to run with Capture mode.

There’s some information on cleaning up content here:

https://ssl.webaware.net.au/testing/cleaning-up-content/

Essentially though, if you’re getting insecure content warnings from content on your website, you can usually clean those up by doing a search and replace with Better Search Replace. Read the section “Images, iframes, embeds” on the link above. And please take a backup first!

cheers,
Ross

G’day @pframe,

Thanks for the bug report! I couldn’t replicate it on my multisite dev environment, had to go to a single site to see it. I’ve fixed it for the next release, and you can get a preview of it here if you like:

https://www.dropbox.com/s/8ban14o77q5a9nv/ssl-insecure-content-fixer-2.3.1-dev.zip?dl=1

cheers,
Ross

G’day @justine13,

This plugin does not run a scan. Are you talking about the HTTP detection on the Settings screen? Or perhaps the SSL Tests screen? Neither run a scan, they just check for indications of WordPress detecting HTTPS:

https://ssl.webaware.net.au/https-detection/

cheers,
Ross