Title: [Plugin: Links shortcode] SSL insecure content
Last modified: August 20, 2016

---

# [Plugin: Links shortcode] SSL insecure content

 *  Resolved [webaware](https://wordpress.org/support/users/webaware/)
 * (@webaware)
 * [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-links-shortcode-ssl-insecure-content/)
 * This plugin is loading its CSS using the WP_PLUGIN_URL constant instead of the
   plugin_dir_url() function, so it triggers insecure content warnings on SSL pages.
   I’ve added a “fix” for this plugin to my [SSL Insecure Content Fixer plugin](http://wordpress.org/extend/plugins/ssl-insecure-content-fixer/),
   but you should make the following changes to avoid these warnings without the
   aid of my dirty kludge 🙂
 * * use the wp_print_styles action to enqueue your CSS, instead of printing it 
   from wp_head action
    * use plugin_dir_url() to get your plugin dir, instead of
   WP_PLUGIN_URL, so that it handles the transition to SSL (HTTPS)
 * Once you’ve released a version that fixes these, please let me know and I’ll 
   remove the “fix” for your plugin.
 * [http://wordpress.org/extend/plugins/links-shortcode/](http://wordpress.org/extend/plugins/links-shortcode/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [Maarten](https://wordpress.org/support/users/maartenjs/)
 * (@maartenjs)
 * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-links-shortcode-ssl-insecure-content/#post-2752362)
 * Thanks! This issue should be fixed in version 1.3 released today.
 *  Thread Starter [webaware](https://wordpress.org/support/users/webaware/)
 * (@webaware)
 * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-links-shortcode-ssl-insecure-content/#post-2752363)
 * G’day Maarten, thanks for the update. I’ve removed my dirty kludge for your plugin
   now!
 * I haven’t tested, but you might look at the Facebook button that you’re loading.
   It’s loaded with http: which means it could trigger SSL insecure content warnings
   too. It will probably work OK if you use the protocol-free URL, i.e. drop http:
   but leave // — but please test.
 * cheers,
    Ross
 *  Plugin Author [Maarten](https://wordpress.org/support/users/maartenjs/)
 * (@maartenjs)
 * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-links-shortcode-ssl-insecure-content/#post-2752364)
 * Thanks! I’ve added that change in the next release. I have no possibility to 
   test it on an https site, but in a normal http site it works.
 *  Thread Starter [webaware](https://wordpress.org/support/users/webaware/)
 * (@webaware)
 * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-links-shortcode-ssl-insecure-content/#post-2752365)
 * G’day Maarten, if you zip it up and post a link to it here, I can test it for
   you (I’m on Fedora Linux, which comes with a generic SSL certificate).
 * cheers,
    Ross
 *  Plugin Author [Maarten](https://wordpress.org/support/users/maartenjs/)
 * (@maartenjs)
 * [13 years, 3 months ago](https://wordpress.org/support/topic/plugin-links-shortcode-ssl-insecure-content/#post-2752396)
 * Hello webaware,
 * Sorry for the delay. I have attempted to fix the issue. Please let me know if
   you still encounter it in yesterday’s 1.4 release.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘[Plugin: Links shortcode] SSL insecure content’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/links-shortcode_99cefc.svg)
 * [Links shortcode](https://wordpress.org/plugins/links-shortcode/)
 * [Support Threads](https://wordpress.org/support/plugin/links-shortcode/)
 * [Active Topics](https://wordpress.org/support/plugin/links-shortcode/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/links-shortcode/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/links-shortcode/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [Maarten](https://wordpress.org/support/users/maartenjs/)
 * Last activity: [13 years, 3 months ago](https://wordpress.org/support/topic/plugin-links-shortcode-ssl-insecure-content/#post-2752396)
 * Status: resolved