Closed (fixed)
Project:
Glossary
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
5 Jun 2007 at 02:46 UTC
Updated:
20 Feb 2008 at 16:16 UTC
Thank you to the developpers of this module. It looks to be very useful. Can anyone let me know how to accomplish the following:
1) Increase the allotted size for the on hover pop-up definitions. My glossary terms cannot fit the one line provided.
and
2) Replace the link to the taxomony term in the glossary itself to a node.
Comments
Comment #1
brasto commentedI second this request. A couple notes:
1. The on-hover popup definition works differently in Firefox and IE. IE seems to give the whole definition for my longer strings, but Firefox cuts off the definition.
2. This page does what I want: http://flfn.org/glossary ; and if I click "View" next to a glossary, I also get a page that makes sense. However, if I click "Detailed definition", I don't get the definition - I get a listing of all the available pages that include that term. I'd rather either go to a node that includes the definition, or to a page that shows the term's "details" field.
Comment #2
tanoshimi commented1.) The on-hover definition is provided using the 'title' attribute of a standard url link, or the 'title' attribute of an acronym tag if choosing the acronym replacement method, so as brasto has mentioned - this will depend on how your browser handles these.
2.) "Detailed Definition" link points to taxonomy/term/tid of the term in question - which by default lists all nodes tagged with that term. You can override this though using taxonomy_redirect module and point this to a view which includes the term's definition or whatever you want.
Comment #3
nancydruIMHO, "Detailed definition" does not mean "show me all nodes tagged with this term." I would consider this a bug.
Comment #4
brasto commentedI echo that humble opinion. I finally moved on to the alinks module. It does not have all the features I'd like, but at least it goes to the page I tell it to, and someone is actually working on that module. Nobody's done anything on this one for months.
Comment #5
nancydruI've "talked" to Moshe and he is busy on other things. I'm going to try to be a bit more active on this and get some patches submitted. Perhaps one of these days, he'll allow me to commit them.
Comment #6
nancydru@duncra, tanoshimi - read my explanation (#3) in http://drupal.org/node/182937.
#2 is "by design"
Comment #7
nancydruComment #8
nancydruI have done a fair bit of research on this, and, reluctantly, I have to mark this as "won't fix" because it is browser specific and beyond the scope of this module. If someone has a magic, cross-browser solution, I'd be happy to revisit the issue.
Comment #9
brasto commentedThis is actually 2 bugs. One is browser specific, and there's a plugin for Firefox to fix it. However, the second one is not browser specific. I visited the link with the fix/workaround for #2 and I'll give that one a try. However, I think it should probably be re-designed if indeed it is by design, because it seems counter-intuitive. What if I want to use the Glossary term without linking it to the definition? I should be able to assign it to the category if I want it to link to the definition and not assign it if I don't want it to. That seems more the way taxonomy is designed to work, but maybe I misunderstand.
Comment #10
nancydru#1 - Which plug-in? I saw one that allowed FF to "incorrectly" display the alt tag as a tool-tip (as IE does). I didn't see one that increased the size of the tool-tip itself.
#2 - I'm not entirely sure I understand you here. The "Glossary" vocabulary is for displaying a Glossary, as this module does. It is not for selecting lots of content. If you want to tag content with the same term, it will show up when you click the "taxonomy/term/xx" link that is generated. This is the definition of "Detailed description." If you want Glossary to work the way it does now AND have "taxonomy/term/xx" work differently, you will need two vocabularies, perhaps with the same terms. Or, possibly, the Taxonomy Redirect module will help you.
I am always open to discussion, but perhaps this ought to be moved into a separate issue.
Comment #11
brasto commentedHere's the Firefox fix, called "Long Titles":
https://addons.mozilla.org/en-US/firefox/addon/1715
With the fix and explanation you posted for the second issue, I'll give that a try, and if I see the need for another enhancement request, I may file it, but you're right, it should be a separate issue/bug/enhancement request. It should have been filed separately in the first place.
Comment #12
nancydruThanks, Brasto, I downloaded that add-on, and things are much better. I'll mention that in my documentation.
Comment #13
nancydru