safecss and HTTPS mixed content errors. Fix included.

  • Dan Collis-Puro

    (@djcp)


    14 years ago

    A minor change is needed to make safecss work properly when a site is being viewed under HTTPS context – otherwise it’ll use “siteurl” directly from wp_options which, in all likelihood, is using the http:// protocol. This will cause mixed content errors and browsers will throw up scary looking “site not secure! omgwtfbbq” errors.

    On line 433 of safecss/safecss.php, replace:
    $href = get_option( 'siteurl' );

    to:

    $href = site_url();

    http://ww.wp.xz.cn/extend/plugins/safecss/

Viewing 1 replies (of 1 total)
  • Brian Zoetewey

    (@omicron7)

    13 years, 9 months ago

    If using the “Start from scratch . . .” option, then line 452 needs to change as well.
    from:
    return 'http://' . $_SERVER['HTTP_HOST'] . '/wp-content/plugins/safecss/blank.css';
    to:
    return plugins_url( 'blank.css', __FILE__ );

Viewing 1 replies (of 1 total)

The topic ‘safecss and HTTPS mixed content errors. Fix included.’ is closed to new replies.