jQuery update doesn't over write misc/jquery.js

I am wondering something similar. Perhaps this is a more basic question.

I noticed a problem encountered with JQuery in views with many links when using Firefox. Basically the javascript in the view is timing out when there are 100 or 200 links (rows) on the view. So I hope that perhaps an updating JQuerying will fix something.

Then I hear about JQuery Update and then I wonder why Drupal ships with an old version of JQuery (1.2.6).

I'm running JQuery Update 6.x-1.1 on a Multisite and I don't see any update happening to /misc/jquery.js or mysite/modules/jquery_update/replace/jquery.js. They are each 1.2.6.

Can anyone shed some light why all this is the way it is?
Why don't people just copy some recent supported version of jquery.js to the /misc directory on their server? And which version would that be?

Thanks,

-dave

I'll try to answer some of your questions:

Then I hear about JQuery Update and then I wonder why Drupal ships with an old version of JQuery (1.2.6).

I believe Drupal ships with such an old version of jQuery because that was the current version when Drupal 6 was released, and updating jQuery in the core would require all contributed modules to be compatible with the new version of jQuery. Drupal 7, I believe, will be up to date with jQuery.

I'm running JQuery Update 6.x-1.1 on a Multisite and I don't see any update happening to /misc/jquery.js or mysite/modules/jquery_update/replace/jquery.js. They are each 1.2.6.

When you install the jQuery Update module, you are supposed to manually download the version of jQuery you want to use, then upload it to the sites/all/modules/jquery_update/replace/ folder, renaming them jquery.js, jquery.min.js, and jquery.pack.js depending on when version you are using, etc.

Why don't people just copy some recent supported version of jquery.js to the /misc directory on their server? And which version would that be?

Making changes to the Drupal core code is generally undesirable and can make for difficult updates. Once you start making change to the core, you have to keep track of them if you are going to update the site later on, and you're going to have to remember that you are keeping track of such changes. It really doesn't pay off in the end to modify the core if you can help it.

Hope this helps.

When you install the jQuery Update module, you are supposed to manually download the version of jQuery you want to use, then upload it to the sites/all/modules/jquery_update/replace/ folder, renaming them jquery.js, jquery.min.js, and jquery.pack.js depending on when version you are using, etc.

Why isn't this documented in README.txt or INSTALL.txt?

I think people are confused about jquery update 6.x-1.1. It doesn't do anything anymore, because the version included is same like drupal core.

Also after upgrading from 6.x.1.1 to 6.x.2 beta, don't forget to flush your cache. Everything works then

@uberhacker : I think that's because jquery v2 ships with the latest compatible jquery version usually.

I agree... spent way too long trying to figure out this module's functionality

Drupal 6 reached EOL (end-of-life) on February 24, 2016.