Title: Flickr widget needs to be updated to work over HTTPS
Last modified: August 21, 2016

---

# Flickr widget needs to be updated to work over HTTPS

 *  Resolved [estr](https://wordpress.org/support/users/estr/)
 * (@estr)
 * [12 years, 8 months ago](https://wordpress.org/support/topic/flickr-widget-needs-to-be-updated-to-work-over-https/)
 * Hello,
 * Currently, Flickr widget can work on sites that use HTTPS instead of HTTP.
 * The following needs to be changed for it to work:
 * `<script type="text/javascript" src="http://www.flickr.com/badge_code_v2.gne?
   count=';`
 * to
 * `<script type="text/javascript" src="//www.flickr.com/badge_code_v2.gne?count
   =';`
 * and then it will work over both HTTP and HTTPS.
 * Please update!
 * Thanks!
 * [http://wordpress.org/plugins/gabfire-widget-pack/](http://wordpress.org/plugins/gabfire-widget-pack/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Gabfire](https://wordpress.org/support/users/gabfire/)
 * (@gabfire)
 * [12 years, 5 months ago](https://wordpress.org/support/topic/flickr-widget-needs-to-be-updated-to-work-over-https/#post-4147332)
 * Sorry for delay but thanks for the contribution estr. The plugin is updated

Viewing 1 replies (of 1 total)

The topic ‘Flickr widget needs to be updated to work over HTTPS’ is closed to new
replies.

 * ![](https://s.w.org/plugins/geopattern-icon/gabfire-widget-pack_f4f4ee.svg)
 * [Gabfire Widget Pack](https://wordpress.org/plugins/gabfire-widget-pack/)
 * [Support Threads](https://wordpress.org/support/plugin/gabfire-widget-pack/)
 * [Active Topics](https://wordpress.org/support/plugin/gabfire-widget-pack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/gabfire-widget-pack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/gabfire-widget-pack/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Gabfire](https://wordpress.org/support/users/gabfire/)
 * Last activity: [12 years, 5 months ago](https://wordpress.org/support/topic/flickr-widget-needs-to-be-updated-to-work-over-https/#post-4147332)
 * Status: resolved