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.
- This topic has 3 replies, 2 voices, and was last updated 8 years, 10 months ago by
Steven Zahm.
-
AuthorPosts
-
10/28/2014 at 3:40 pm #308394
Susan
ParticipantOur theme is currently running jQuery 1.7.1, which is causing problems, so I’m testing what happens updating to 1.11.1. We’re using a customized version of the cMap template.
If I update the jQuery call to 1.11.1 the bio dropdown does not work using either cMap or our customized version. Both work when the jQuery call is 1.7.1.I tried disabling the Bootstrap js call and turning off WPBakery Visual Composer, which is the only recent plugin change we’ve made. Neither fixes the issue.
Thanks, Susan
10/29/2014 at 10:04 am #308420Steven Zahm
Keymaster@ Susan
Connections is compatible with jQuery 1.11.1 (which is what is used on this site).
I suspect you may have multiple jQuery versions being loaded on the page which is actually causing the problem.
Looking at the page source I see this:
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js"></script>
<script>window.jQuery || document.write('<script src="/wp-content/themes/roots/js/libs/jquery-1.7.1.min.js"><\/script>')</script>I would say this is a very bad way to handle this within WordPress. It’s always better to let WordPress manage jQuery and let it load the version that is bundled with WordPress. Loading jQuery via a CDN is fine when done correctly, it is just the above is not correct (for WordPress). This probably why you’re having problems with jQuery in general.
Here’s an excellent blog post which goes into deep detail:
https://pippinsplugins.com/why-loading-your-own-jquery-is-irresponsible/Fixing this could be easy or tough…
First, I would remove the code I referenced above. My guess is that is it will be in the theme’s
head.php
orheader.php
file.Now it seems some is de-enqueuing the bundled jQuery version. So this is the tough part. If you know what is de-enqueuing it, disable it. If you do not, Connections has something built in which attempts to fix this issue. Go to the Connections : Settings admin page and click the Advanced tab and enable the jQuery option.
Hopefully this fixing the issue.
If you wish to load jQuery from a CDN, use only this plugin:
https://wordpress.org/plugins/use-google-libraries/Hope this helps! Let me know.
11/03/2014 at 1:03 pm #308888Susan
ParticipantThanks for the info and the link. I inherited the current jQuery setup and I’ve been trying to test what will break if I update. Enabling the jQuery option in Connections does fix the directory problem, but the list of other elements that break and conflicts I haven’t been able to isolate is growing as I investigate. Since we’ll be undergoing a major rebuild in the next 6 months I may have to hang on to the current setup til then.
Thanks again, Susan11/04/2014 at 8:32 am #308951Steven Zahm
Keymaster@ Susan
Yeah, that does sound like the best option.
-
AuthorPosts
You cannot reply to this support topic. Please open your own support topic.