[Plugin: Use Google Libraries] load jquery 1.7?

The version numbers come from WordPress core, and I’m not going to change that because it would break pretty much everything.

Shouldn’t it load the version that is used in the skins? Provided the version number is declared properly.

I’d say use core if not declared, but if declared, use the declaration.

Great plugin by the way. Saves me from having to do this by hand in the functions.php file and does it for other libraries I never thought to look for. Thank you.

Time to resurrect this thread. I’m having an issue with UGL not loading the version from WordPress core. It’s loading the current Google AJAX API: v1.8.0 and the drag-and-drop stopped working again because WP doesn’t understand v1.8x.

And, it’s loading https on non-https posts/pages. Waiting for the Transients API to timeout after disabling and enabling the plugin to see if that fixes anything.

Having the Transients in the mix, while trying to hunt down causes, is a pain. Looked for ways to manually expire and delete them but the solutions looked to be too scary to attempt.

Seems that the Transients API timeout took care of the versioning problem. It’s now loading jQuery v1.7.2 and drag-and-drop works again. That’s always the first thing to break if you load a more recent jQuery version. It’s be great if the devs could make the admin code a bit more tolerant of newer versions.

Still is calling through the https protocol, though. Does it switch to https if there is anything on the page that is loaded using that protocol? With Twitter Anywhere loading its own duplicate, dumb versions (v1.4.4) in both http and https “because we want to know what we’re working with” (how about the current one?) so we’re all stuffed with THREE jQuery libraries, could that be what is triggering UGL to call https?

Is your admin loaded over https?

I thought the http/https selection was processed after the URLS were loaded from the transients, but it’s possible it’s not. I’ll have to look at the code and see.

Ok, I ran through everything I could think of, and I can’t make this happen (loading over https when it shouldn’t). Can you verify it’s actually in your page source as https, and not some browser plugin/extension/whatever causing all traffic to google.com to go over https?