Insecure content on HTTPS site

[alexgieg]

I've started testing Swift on an HTTPS-enabled site, and noticed Google Chrome giving warnings about insecure content. Digging around (pun intended), I found it's related to some code in js/swift-scripts.js for an (unused?) Digg button. Commenting-out or deleting lines 188 to 201, then saving the settings, did the trick, and now most pages aren't reporting insecure content anymore.

I hope this helps!

[Satish]

Thanks Alex, howz your store coming up?

[alexgieg]

It's basically done. All that's needed now is to make credit card payments work. The gateway I'm using doesn't provide a WP e-Commerce plugin, only a generic PHP library, so I'm having to integrate the later into the former myself. Once that's done the site goes live.