Support has been upgraded!
The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Premium Support
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Free Support
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
Tagged: 8.5.7, css, javascript, plugin conflict, WP Minify
- This topic has 1 reply, 2 voices, and was last updated 10 years, 7 months ago by
Steven Zahm.
-
AuthorPosts
-
12/30/2015 at 3:34 pm #359452
Aaron Silver
GuestSteve,
When I updated to Version 8.5.7 from Version 8.2.8, my website broke because it stopped loading any styles. I was able to hunt down the problem to Connections. The style it’s trying to load is showing up with a bad path:
<link rel='stylesheet' id='cn-chosen-css' href='//bjnyc.staging.wpengine.com/wp-content/plugins/connections/vendor/chosen/chosen.min.css?ver=1.4.2' type='text/css' media='all' />It should have http: in front of the URL, like all the other css URLs that load into the site. (The website actually broke, and loaded no css at all, because we’re using wp-minify, and the minified URL it produces is broken because of this one bad URL).
I hunted around a little bit in the connections PHP, and found a variable $url which is used when enqueueing the stylesheet. $url is produced on line 222 of class.scripts.php:
$url = cnURL::makeProtocolRelative( CN_URL );I stopped hunting at that point.
Can you help solve this?
Thanks,
Aaron.12/30/2015 at 6:37 pm #359469Steven Zahm
Keymaster@ Aaron
That is correct, that is a standard supported by all browsers and WordPress for quite some time. It is a protocol relative URL. This allows the asset to be loaded over either
httporhttpswithout browser throwing mixed content warnings.So, in short, this is not a bug with Connections. It is a bug in WP Minify not properly supporting assets that were enqueued with protocol relative URLs. If WP Minify has an option to exclude files, then I suggest try adding this file as an exclusion. The assets loaded by Connections are already minified anyway.
Hoe that helps!
-
AuthorPosts
You cannot reply to this support topic. Please open your own support topic.
