Posted by nicholas.alipaz on October 28, 2009 at 7:22pm
Jump to:
| Project: | jQuery UI |
| Version: | 6.x-1.3 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
I suggest changing the location of the library in order to get in sync with upcoming D7, and to better ease the upgrade process of jquery_ui module.
Here is a patch that moves jquery.ui to the sites/all/libraries or sites//libraries folder. It also adds a dependency for the libraries module. the only thing that was odd was I needed to do an include_once for the libraries.module file. This may be able to be worked around by adjusting the module's weight.
| Attachment | Size |
|---|---|
| jquery_libraries.patch | 2.89 KB |
Comments
#1
oh, btw. I patched this against 1.3, simply because it is what I had on my machine. It may need to get remade against dev.
#2
That should have read:
Here is a patch that moves jquery.ui to the
sites/all/librariesorsites/<domain>/librariesfolder#3
Thank you. I have never been able to install jquery.ui I keep getting an error that the jquery.ui is not there (installed the contents of the compressed file into /sites/all/modules/jquery_ui/jquery.ui as specified and it says very clearly that it's not there - at the top of the modules list in pink just after you check the box next to jquery ui and it as a result unchecks the box also, of course deactivating the module, never had a module that instantly unchecked itself, you are supposed to check for dependencies before even allowing the module to be checked-- the libraries are there just as specified but it goes into this mode of rejection as if they were not there) No matter what I do and I've tried everything. Quite a number of other people are having the exact same problem as I am and the people supporting the module in drup are not responding or just saying things like "you don't know how to install a module" .. "it worked for me so it should work for you" The only sense i can make is there is possibly some conflict between some other module that is relatively commonly used.
#4
Tigerboy, your post does NOT relate to my patch. Please post in your own support thread. This patch is simply to move the jquery.ui library to a different directory.
On a side note the reason you can't get help is that you are saying, "It doesn't work" without having any real way to reproduce the problem. Please post in your own thread.
#5
Sorry to invade your thread, I had thought it did have relevancy. But since you chose to comment on my unideally posted thread: I very carefully and clearly stated what happened, I didn't just say "it doesn't work".
This is just another example of the drupal forums being filled with people that actually post things to criticize other people's post's rather than simply trying to help them. The purpose of the fora area is to help people. My post was about jquery.ui and I feel it was very relevant. Maybe I'm exaggerating slightly but it seems like the Drupal fora areas are over 90 percent non-helpful responses.
#6
I know you didn't, just say "it doesn't work." However, without some sort of error log, some other sort of symptom, steps to reproduce, operating system of the server, php version, or other environmental variables as well as drupal/module version numbers there is really no way for anyone to help you.
Please open a new thread (as a support request) with similar info (in this module's issue queue) and you should find help here.
#7
what error log?? As I stated I placed the files exactly as specified and the "error condition" is the module installer claims the file it's looking for isn't where it actually is and prevents the module from being activated. I check the jquery.ui box in the modules list, hit save at the bottom and the jquery.ui proceeds to uncheck the module and complain that the module is not located exactly where it is located in a little alert message at the top of modules. File permissions and ownership are all fine. Anyway I'm very interested in resolving this but I do have other projects I'm working on so this has become something of a back burner issue for me. Thanks.
#8
Thanks for taking the time to report this issue.
However, marking as duplicate of #489140: Libraries API. Please search for existing issues before submitting a new one.
You can follow up on that issue to track its status instead. If any information from this issue is missing in the other issue, please make sure you provide it over there.