Unneeded dependency on jQuery Update

Looked up the issue for other modules which depend on jquery update (e.g jQuery UI) and will follow what happens there.

See the discussion at http://drupal.org/node/283968

Is there a more specific reason why jQuery Update is needed?

I'm optimizing my sites performance and jQuery that comes with Drupal is 31K while jQuery update is 55.7K minified. I'm going to go with Drupal's default, since I'm not having any issues. This might be because Drupal's jQuery version is packaged.

I recommend removing the jQuery Update dependency and just documenting on ddblock's project page that ddblock is only compatible with Drupal 6.3+ because ddblock required jQuery 1.2.6.

There is no use overriding something that doesn't need to be overridden. Keep in mind, that issue was closed in 2008. Now Drupal is at version 6.16. I can't imagine someone trying to using something before Drupal 6.3 now in 2010.

Apparently, jQuery Update uses the default jQuery shipped with Drupal 6.3+ when selecting "packed" in the jQuery Update.

So this means there really is no reason to depend on jQuery Update when using Drupal 6.3+.

subscribe

Hey there,

Jquery update is breaking my fusion based custom theme so I can't run it with Jquery update. Would the module still work if I remove the dependency manually? - It looks like it does from what I can read in this thread but I want to make sure before I do something silly that might break my site. I also just bought a commercial theme to install before I realised of the dependency. Do I need to nodify anything else apart from the *.info file?

Thanks in advance for any support

Raul

#6
You only need to remove the dependency for jquery update from the .info file.
The module would run without jquery update.

Thanks for the quick reply!

Raul