WordPress.org

Ready to get started?Download WordPress

Forums

Links shortcode
[resolved] SSL insecure content (6 posts)

  1. webaware
    Member
    Posted 1 year ago #

    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, 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/

  2. Maarten Swemmer
    Member
    Plugin Author

    Posted 1 year ago #

    Thanks! This issue should be fixed in version 1.3 released today.

  3. webaware
    Member
    Posted 1 year ago #

    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

  4. Maarten Swemmer
    Member
    Plugin Author

    Posted 1 year ago #

    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.

  5. webaware
    Member
    Posted 1 year ago #

    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

  6. Maarten Swemmer
    Member
    Plugin Author

    Posted 1 year ago #

    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.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic