=== Protocol Relative Theme Assets === Contributors: ryanjbonnell Author URI: https://github.com/ryanjbonnell Plugin URI: https://github.com/ryanjbonnell/Protocol-Relative-Theme-Assets Donate link: https://www.gittip.com/ryanjbonnell/ Tags: stylesheet, javascript, script, protocol, relative, url, http, https, ssl, css, js, scheme, asset, style_loader_src, script_loader_src, template_directory_uri, stylesheet_directory_uri, enqueue Requires at least: 3.6 Tested up to: 4.0 Stable Tag: 1.0 License: GPLv2 or later License URI: http://www.gnu.org/licenses/gpl-2.0.html Transforms enqueued CSS and JavaScript theme URLs to use protocol-relative paths. == Description == This plugin transforms any registered, enqueued CSS or JavaScript URLs into their "protocol-relative" equivalent. Consider the following examples: **Protocol Relative CSS URL** `` **Protocol Relative Javascript URL** `` More appropriately called a "network-path reference" or "scheme-relative path", a protocol-relative URL helps to avoid common scenarios such as: * Broken SSL padlock icon in browser's address bar when showing mixed HTTP/HTTPS content * Error message in Internet Explorer saying, "This Page Contains Both Secure and Non-Secure Items" * Serving HTTP assets when viewing HTTPS pages The idea of using protocol-relative URLs was popularized by [Paul Irish](http://paulirish.com/2010/the-protocol-relative-url/) and has become common as sites switch between serving HTTP and HTTPS assets. This plugin will standardize all properly enqueued theme files to use protocol-relative paths, even those added from third-party plugins. _Note: This plugin does not transform any image paths that may be embedded in the WordPress editor or output as featured images or elsewhere in the theme -- it presently only works on enqueued CSS/JavaScript files._ == Frequently Asked Questions == == Upgrade Notice == == Screenshots == == Installation == 1. Activate the plugin through the Plugins menu in the WordPress admin. == Changelog == = 1.0 = * Initial release