https://legacy.forums.gravityhelp.com/topic/queued-scripts-and-styles-use-the-wrong-protocol Gravity Support Forums Topic: Queued scripts and styles use the wrong protocol en-US Sat, 04 Apr 2026 11:06:57 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/queued-scripts-and-styles-use-the-wrong-protocol#post-54617 Mon, 09 Apr 2012 11:23:13 +0000 Alex Cancado 54617@https://legacy.forums.gravityhelp.com/ <p>This seems to be a problem isolated to your configuration. In my local install the scripts do get enqueued with the correct protocol. I am not sure if the WordPress HTTPS plugin is the one causing the issue, but one suggestion I have is to go through the plugin conflict process to determine where the conflict is.<br /> <a href="http://www.gravityhelp.com/documentation/page/Testing_for_a_Plugin_Conflict" rel="nofollow">http://www.gravityhelp.com/documentation/page/Testing_for_a_Plugin_Conflict</a><br /> Once we determine what is causing the issue, I can dig deeper and figure out why. </p> https://legacy.forums.gravityhelp.com/topic/queued-scripts-and-styles-use-the-wrong-protocol#post-54461 Fri, 06 Apr 2012 11:16:57 +0000 developdaly 54461@https://legacy.forums.gravityhelp.com/ <p>When Gravity queues scripts or styles for loading on the frontend and admin side it is doing so using the wrong protocol, so the end result is loading http:// resources on a secure page, giving the user warnings.</p> <p>I checked that you're using <code>plugins_url()</code> to determine the plugin's path, so I'm not really sure why it's not being respected. The most likely cause is that my SSL plugin is firing after Gravity. Do you guys have any experience with that being the case with the WordPress HTTPS plugin?http://wordpress.org/extend/plugins/wordpress-https/ </p>