Readme.txt: "Place the extracted contents of the library into /path/to/qtip/library"

Not clear to me what to do; drupalroot/path/etc. gtip/path/etc ?

Both don't exist however & it could be directly in the module without subdirs too?

Then there is a Drupal policy that libraries should go into /sites/all/libraries instead, although I haven't seen that much happen for JS/jQuery and maybe is excluded or not from that policy?

Also there is a js file that is used in many modules and is just the same. No you don't have that file, but a possible point is what happens if the same .js files get used on several different locations?

Then I noticed that the latest Drupal release started making a new directory /js that now only contains gmap_markers.js

So where should this go; now and in future?

Comments

ClearXS’s picture

ClearXS commented

Most logically to me seemed to strip down the extracted folder name to "jquery-qtip", so I get:

sites/all/modules/qtip/jquery-qtip:
* jquery-1.3.2.min.js
* jquery.qtip.1.0.0-rc3.js
* jquery.qtip.1.0.0-rc3.min.js
INSTALL
LICENSE
REQUIREMENTS

But I think it might be better (with all other js and jquery) into sites/all/libraries/jquery-qtip

Now looking if it works; ticking the module on =>
"qTip plugin not found! Download the qTip jQuery plugin and read this module's README.txt file for proper installation procedures."

OK, moving to: sites/all/modules/qtip/path/to/qtip/library

ahh... when renaming folder "jquery-qtip" to "library", IT WORKED. So you meant path-to/qtip/library, or sites/all/modules/qtip/library...

ClearXS’s picture

ClearXS commented

So making an article editing a story and put there:

[qtip:cheking qtip test|Works: Text to appear in tooltip]

and yes; it works!

I don't know why I don't get the option anymore, that I had in my former installation, where all these additional codes/filters were explained; suppose it gets automatically in that editing code overview for users that want to post articles and comments.

Would be nice if this can be integrated with the WYSIWYG module using CKEditor plugin etc. ..?

Then how to get this on other places of the website that are NOT nodes? Like menus?

bocaj’s picture

bocaj commented

Sorry ClearXSClearXS. For some reason I was not getting notifications of issues for this module (should be fixed now). Anyway, I apologize for my mis-communication. I was actually thinking as well that the qtip plugin code would probably be better served in sites/all/libraries. For now the library is supposed to go in sites/all/modules/qtip/library. Looking back on this I was not clear at all in my description.

I have not had time to fully read your posts above. Please give me a little time and I will have a more detailed response for you. I just wanted to quickly respond since I see that this has been hanging out there for a few days.

bocaj’s picture

bocaj commented

Like I posted before, I think the change to sites/all/libraries is a good move.

I am always looking for new functionality to look into incorporating into the module. I like the idea of using qtips in non-node sections. There is actually a module being submitted for review by someone else that handles the menus you were referring to. I am not sure of the status of that module or how it is implemented. I believe it is dependent on Panels.

I am always open to suggestions to make the module more useful and beneficial for everyone that uses it. Please feel free to comment on any feature requests/ideas that you may have. Of course any bug reports are good as well!

bocaj’s picture

bocaj commented
Status: Active » Fixed

This issue has been fixed in beta1. Thanks!

ClearXS’s picture

ClearXS commented
Status: Closed (fixed) » Fixed

Thanks to you; I like the module very much!

It's only a mess on Drupal where plugins etc are located. A lot of modules have the JavaScript/jQuery still in their module. I'm not sure if they all should go in sites/libraries, as there is almost no JS/jQuery there right now. But maybe it should be there for libraries that don't come automatically with the module, while developers who incorporate these in their module releases can have them within the module. Then I saw a new Javascript directory automatically being made in the latest Drupal releases.

"I don't know why I don't get the option anymore, that I had in my former installation, where all these additional codes/filters were explained"
=> I found that all filter were under Flexifilter that I'd installed, so there I could activate qTip for WYSIWYG/CKEditor. Only hope that CKEditor through WYSIWYG shows some editing button for it, instead of that I need thinking every-time about how to code it.

Not that much to open a new issue, but I read in the new readme.txt (not on the project page) that only jquery.qtip-1.0.0-rc3.min.js is used, while my download contained:
* jquery-1.3.2.min.js
* jquery.qtip-1.0.0-rc3.js
* jquery.qtip-1.0.0-rc3.min.js

=> what are the others for?

I removed them without problem. But when removing jquery.qtip-1.0.0-rc3.min.js I still get a smaller white standard drupal tooltip; the same one can see hovering over a link and shows the real url. Is that Drupals standard? Its also used for text instead of url's sometimes:
http://mi-cr.org/content/test-articulo-1-nuevo-diferente-basico

Edit Jan 18th: I don't know how I got a new /js directory in the root of drupal 6.19, as there ain't any in drupal 6.20. Only gmap_markers is in it and a search indicates that it probably has got there eronomous by a mistake from my hand.

Status: Fixed » Closed (fixed)

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

shinz83’s picture

shinz83 commented

I still have no idea where to put the library. I am trying to use qtip functionality with the Menu Minipanels module. I have put the library everywhere in my folders and nothing seems to work.

Any advice?

bocaj’s picture

bocaj commented

shinz83: This module is completely independent of the Menu Minipanels module. You do not need this module to use Menu Minipanels and visa versa. I can only suggest visiting the Menu Minipanels project page and creating an issue there. It appears that your issue can be answered on the project page, under Installation.

Sorry I can't be of any more help, but I have actually never used that module.

Status: Fixed » Closed (fixed)

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