Hi,

My custom theme uses jQuery 1.7.1 - and I am having issues with colorbox module compabilty with that version. Colorbox conflicts with the 1.7.1 simply does not load.

Now I hoped that jQuery Multi can solve the problem, but when I upload an older version (say 1.4.4) to jQuery Multi - and select Colorbox to use it (somehow there is a checkbox to select it - very nice!) - it still generates the same error as before and does not load. I tried it with multiple versions, and it seems that something works not like it was intended by you.

I even tried to delete the original 1.7.1 jQuery from the themes folder, and load it globally with your module, but that seems not to work as well - my themes drop-downs go South. So it seems that the module does not do what it is supposed to - load the X version of jQuery either for selected Module or globally.

It would be also cool to have an option to load more than one jQueries for different modules (say 1.4.4 for Colorbox and 1.5.2 for XXXX when the theme itself can uses 1.7.1)

P.S. I have done multiple Cache clears as well as Browser Cache was emptied each time - all same.

Thanks for the work and a hopefully a great module.

Comments

goron’s picture

goron commented

A few things:

  • The 'load always' setting doesn't load the new jQuery globally, for the whole site. It simply loads jQuery whether or not you select files to target to it using the UI or hooks. So checking that box will not affect anything unless you use the provided alias in your custom JS (see the README)
  • The ability to load more than one version - I would like to do this, but I don't see it as very important. If it's important to you, please open a new feature request for it so we can keep track of that separately.

Ok. So you say your theme uses jQuery 1.7.1. How are you doing this exactly? It seems that you are essentially replacing Drupal's jQuery 1.4.4 with 1.7.1. This is likely not a good idea, because using jQuery 1.7.1 with Drupal will break all kinds of things, including contrib modules like Colorbox and elements of View UI, as well as parts of core like tabledrag.js and more. This is not recommended. That is the reason this module exists.

The ideal way to do it would be to instead leave Drupal jQuery (1.4.4) loading for everything, and use jQuery Multi to use jQuery 1.7.1 for any of your theme functionality that needs it.

To accomplish this you have two options:

  1. Use hook_jqmulti_files(). Implement this in your own module and include the files from your theme that need to work with jQuery 1.7.1.
  2. Check the 'load always' checkbox on the config form and then use the alias jq171 in your theme JS.

Please see the README for instructions on how to do both of the above, and let me know if you have questions.

goron’s picture

goron commented
Status: Active » Fixed

Marking this as fixed. Please reopen if it doesn't solve your problem.

See also:

#1491300: Better documentation
#1491298: Add ability to target whole themes

von_stirliz’s picture

von_stirliz commented

Hi, Thanks for the feedback,

I have seemed to be able to find a workaround - my theme did not need the 1.7.1 except for one page where the Elastic Slide module was loading. Rest worked fine with Drupals JQ. The problem was that my JS files were not wrapped correctly, so that $ function remained now found when I unloaded the 1.7.1 (which made me think it's a version issue).

So the issue is closed! And thanks for your Module!

Automatically closed -- issue fixed for 2 weeks with no activity.