Title: Unsecure content via HTTPS
Last modified: August 22, 2016

---

# Unsecure content via HTTPS

 *  [vguna](https://wordpress.org/support/users/veitgunagmxde/)
 * (@veitgunagmxde)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/unsecure-content-via-https/)
 * Hi.
 * As posted here:
 * [https://wordpress.org/support/topic/plugin-digg-digg-ssl-support?replies=3](https://wordpress.org/support/topic/plugin-digg-digg-ssl-support?replies=3)
 * running the latest version still calls e.g. the twitter widgets.js via http, 
   although the page is called via https.
    Firefox is complaining about that as 
   an unsecure site. Is there something that fixes this?
 * [https://wordpress.org/plugins/digg-digg/](https://wordpress.org/plugins/digg-digg/)

Viewing 1 replies (of 1 total)

 *  [2bearstudio](https://wordpress.org/support/users/2bearstudio/)
 * (@2bearstudio)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/unsecure-content-via-https/#post-5598288)
 * I am running on the latest version of Digg Digg as well. Mine is complaining 
   the Pinterest javascript load: [http://assets.pinterest.com/js/pinit.js](http://assets.pinterest.com/js/pinit.js)
 * I saw version 5.3.4 update claimed fixing this problem in the changelog. Apparently,
   I wouldn’t call that a fix.

Viewing 1 replies (of 1 total)

The topic ‘Unsecure content via HTTPS’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/digg-digg_9b4479.svg)
 * [Digg Digg](https://wordpress.org/plugins/digg-digg/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/digg-digg/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/digg-digg/)
 * [Active Topics](https://wordpress.org/support/plugin/digg-digg/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/digg-digg/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/digg-digg/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [2bearstudio](https://wordpress.org/support/users/2bearstudio/)
 * Last activity: [11 years, 3 months ago](https://wordpress.org/support/topic/unsecure-content-via-https/#post-5598288)
 * Status: not resolved