I too had to track down the cause of a site acting up and tracked it down eventually to your plugin. Please read up on why it’s best not to do this kind of thing, it’s a very bad practise to force a dequeue of the WP jQuery files for the sake of loading the library from the google CDN which gains very little if you look into things, even if you thought you really had to are you not aware it’s possible to load a current version that stays current with jQuery stable releases.
I would have a read of pipinplugins post on the subject and consider updating your plugin and removing this troublesome bit of code.
http://pippinsplugins.com/why-loading-your-own-jquery-is-irresponsible/
P.S and maybe respond to your support threads 😉
I realize this is a problem and unfortunately haven’t had time to support this free plugin. Truth be told, if there was a way to delete the offering of the plugin I would, because the amount of time it takes to upkeep and respond to support requests is well beyond my bandwidth. I don’t think most people realize that it can become a full-time job (that doesn’t pay anything) to create, update and support a WP plugin. If they did, maybe there wouldn’t be such snide remarks or disapproving comments.
@bkmacdaddy If you wish to have your plugin disabled, send an email yo plugins(at)wordpress(dot)org
Thanks for the tip, Pippin. I ended up taking advantage of the holiday today to fix the jQuery issue mentioned here and have uploaded a new version 2.2.2. Hopefully this will resolve the issues.