Unable to activate module (version mismatch with JQuery UI?)

With the (Drupal module) JQuery UI 1.4 you also have to install the (external library) JQuery UI library version 1.7.x.

Before that, you also need to upgrade the jQuery library that comes with Drupal from 1.2.6 to 1.3.x. To do so, just install jQuery Update 6.x-2.x.

Side note: we deal with Drupal modules and external libraries here, each with its own version number, so please recheck the docs and try to not get confused by this.

Cheers

By providing a link to the proper release of jQuery Update, markus_petrux probably makes my observation unnecessary, but I can report that you DO have to be attentive to the various version numbers swirling around here: I made the mistake of downloading jQuery Update 6.x-1.1 because it was the stable release, rather than the alpha (i.e., in the green section, rather than the yellow), which won't work. Totally my fault, of course, but it cost me about fifteen minutes of worry until I found this thread and realized my mistake.

I can understand your frustration. However, I think this is something to point out to jQuery Update module maintainers. jQuery Update 6.x-1.1 is their recommended version, however it is pointless because it provides the same exact version of jQuery as Drupal 6 itself. They should be advertising, in green, the version of their module that really adds value, which is the one that really upgrades Drupal core.

http://drupal.org/project/usage/jquery_update

If we look at the usage stats, we'll see how many sites do have installed jQuery Update with a version that's really pointless, and that's because their version 2 is not advertised in green.

I already pointed this somewhere in the jQuery Update queue... but I do not have the time to keep fighting for that. :(

http://drupal.org/node/685060#comment-2522684
http://drupal.org/node/685060#comment-2769634
http://drupal.org/node/685060#comment-2882470
http://drupal.org/node/723410#comment-2966854

Sorry if that came across wrong--I wasn't frustrated, really, just confused for a few minutes. But I figured that if I had been confused, others might be, too, so I wanted to pass my experience along to others who might stumble across this thread. Your instructions for upgrading Modal Frame were perfectly correct (as always). If only I, myself, had read your instructions correctly, I wouldn't have had any problems!

(Reading your comments in the threads you linked to, though, the jQuery Update situation does sound like a confusing problem. Oof.)

@highrockmedia

1) Needs review means a patch has been created and needs review and testing. Reference: http://drupal.org/node/156119

2) The project page of the Modal Frame API states it requires jQuery UI library 1.7.x. So you need to install the jQuery UI module, and that particular version of the library. This version of jQuery UI library requires jQuery 1.3.x. Since Drupal 6 ships with jQuery 1.2.6, you have to install the jQuery Update module, but the version that upgrades Drupal to jQuery 1.3.x. This is summarized in the project page of Modal Frame API.

This kind of doubts would have to be addressed by the jQuery UI module. They should describe as accurately as possible how to install the libraries, and which relationships/dependencies each one has with the core jQuery. That's a value that belongs to jQuery UI module.

If anyone else finds doubts with this, please knock the door of the jQuery UI module, or even better try to help in that queue, to find better ways to document the steps to install that module, the library and check its dependencies with jQuery itself.

Should all the other modules that depend on jQuery UI do that job? Why do we want/need a jQuery UI module?

Lack of good documentation means a lot of people is loosing more time than necessary around something that is trivial. :(

The jQuery UI module exists for a reason, and that's to provide a single method to install and use the jQuery UI library. Many modules may depend on that, so it looks more optimal to provide a single place where to document how to install each version of the jQuery UI library with the jQuery UI module, that other modules could refer to, otherwise all those modules will have to repeat over and over the same thing.

If I wanted to make the installation of Modal Frame API easy, I could just packed the jQuery stuff here, but... would that make sense? Do we want to reuse code? May we reuse documentation as well? How can I help better more than one module that depends on X in regards on documentation that is related to X? Isn't it easier to provide X with enough information that those modules can refer to?

For example, if I release something that depends on jQuery UI library 1.6, I'm also telling that jQuery 1.2.6 is enough. Well, not me but the authors of jQuery UI library in their requirements section. If I release something that depends on jQuery UI library 1.7, I'm also telling that you have to install jQuery 1.3.x. Well, not me but the authors of jQuery UI library in their requirements section. They may also document information about other requirements, and those required components may also document information about more requirements... reusing information here is a must, otherwise we are going to document the same thing over and over. And... how many pages would have to be updated when something related to an indirect dependency is changed?

Also, if there's a module that provides a single method to install and use the jQuery UI library, that module should also give you the information on how to install that library, and it should also provide information related to direct dependencies between versions of the library and jQuery itself, because depending on the version of the library you have to install additional stuff, the proper version of the jQuery Update module.

It makes little sense to require this kind of documentation to be provided by each and every module that's going to depend on jQuery UI, and it makes maintenance more complex than it could be.

All this stuff is provided for free, but requires time, and because that's a not an endless resource, it makes sense to think about methods that could optimize that. Note that's not only about my time, but also yours. A single place of documentation about all these matters would have been easier to follow, because it would have been reviewed by a lot more eyes than if all that was documented around a single module that depends on a particular version of jQuery stuff.

Another example... when someone in the Drupal issues queue asks for a patch, that's often enough because people who is going to provide a patch will learn what that means, and how it is done. If not, someone will provide a step by step tutorial or just a link to drupal.org/patch ? That's about information that is well reused...

This thread, or any other post, has the potential to help more people. We use a public forum for that reason, otherwise we would be using private emails. So we're sharing as we discuss... now, where is it more optimal to share a code snippet, somewhere lost in the issues queue of a module, or in the handbooks? ...it's all the same.

Just another note.....when the zip file "jquery-ui-1.7.3.zip" for jquery_ui is downloaded from google and the folder "jquery-ui-1.7.3" is extracted from the zip file, be sure to rename the folder "jquery.ui" and not "jquery-ui". My natural inclination was to just backspace the folder name back to the "ui" part of the foldername and spent some time banging my head on the screen not understanding why I was getting this error message which is sort of misleading. That is a DOT between the "jquery" and the "ui" in the folder name! I know this sounds trivial and stupid on my part but I can just see this happening over and over and over......good luck!

Thank you, thank you, thank you!!! I've been trying to get this to work for half an hour simply because I did the same as you... backspace and not change the name do jqueryDOTui. Ah, how simple some solutions are :)

Had same problem.

Steps described in comment #10 worked fine.

Thanks