Connecting Glossary to Full Node Glossary Entries does not work
| Project: | Glossary |
| Version: | 6.x-1.6 |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Hi,
I'd like to build a glossary (built from taxonomy term descriptions or node teasers or CCK text fields - I don't care about this); the glossary is supposed to display on a long page, aliased to something like ./glossar (or maybe ./glossary); the glossary term headings should be linked to full term entries; something like a default "read more" link would suffice, also; users should be able to work with the glossary (read and edit glossary entries).
According to the documentation, the current glossary module should be able to accomplish this; it reads:
Full Node or "Detailed" Descriptions
Glossary runs on a taxonomy vocabulary and its terms. That means that there is a "Glossary" vocabulary to be used on the node types for which you have it set. Hopefully one of those types is either "page" or "story."
This may be a little confusing at first: You should not assign these terms to the nodes that will have the glossary flagged. Those who have done so have noticed that clicking on the indicator takes them to a "taxonomy/term" page for that term - listing all such tagged content.
The only content that should be tagged with the actual glossary terms are the "full node" ("detailed") descriptions. That way clicking on the link takes you to that full-node description. I would assume that the vast majority of the time there will be only one node assigned with those terms.This is quite unclear. "You should not assign these terms to the nodes that will have the glossary flagged", but: "The only content that should be tagged with the actual glossary terms are the "full node" ("detailed") descriptions." - now what: assign the vocabulary terms to the glossary nodes or not? what is the difference between "flasgging" and "tagging"?
Also, there is an ancient support request about this, dating back to 2007: No Documentation on Full Node Glossary Entries in all of Drupal-land; since this issue was filed for 5.x-1.x-dev it most probably won't be applicable nowadays, at least I can't replicate it.
Currently I have a glossary page that is built through taxonomy terms; glossary nodes of the content type "glossary" are used through the "Node Auto Term" module (NAT) to create a matching taxonomy entry when a new glossary node is created; updating content between "glossary" nodes and taxonomy term descriptions works unreliable and appears to be quite erratic. With the "Taxonomy Delegate" module, users are more or less able to edit taxonomy terms, even if it is more than unpleasant (users are used to create and/or edit nodes).
However, besides that NAT creates glossary terms when glossary nodes are created, there is absolutely no connection between the taxonomy term and the node, it's duplicate content at it's worst. To at least redirect the taxonomy term pages to the glossary nodes, I tried to utilize the Taxonomy Redirect module. Since this module is quite complex itself, I most probably haven't understood correctly what it exactly does, at least it didn't work for me to redirect Taxonomy term pages for terms in the "Glossary" vocabulary to the nodes created through NAT.
Theoretically I could get rid of the "Full Node Glossary Entries", but I'd like to be able to add more content to the glossary descriptions than is displayed on the (long) glossary page, e.g. CCK-based fields; Taxonomy won't support this.
I'd like to know (a) if it is really possible to create Full Node or "Detailed" Descriptions with the glossary module (has anyone made it work?), and (b) if there is any up-to-date tutorial I could follow (the documentation simply says that it is supposed to work but does not explain how to accomplish it).
Thanks & greetings, -asb
#1
Yeah, I've sweated over this, too. Looks like the devs could chime in once in a while and address issues or answer questions. Anyway, here's what I finally did:
1. To prevent confusion and the potential problem mentioned in the docs, I created a new content type called Glossary detail.
2. I associated the Glossary vocabulary to this content type
3. When you create a detailed description node, associate it with the proper Glossary term
Then, when you click on the flagged term, you will go to the Glossary page for that term and there have a link to the full node. Don't know if that's the way it's supposed to work, but that's what it is doing for me.
I'm having trouble with synonyms, and I think it is a bug, but, so far, no answer. So, looks like we're pretty much on our own. It's a great module, though, just the same, and I appreciate all the work that has gone into it.
Hope this helps.
#2
My improvment (I hope).
#3
I needed the same features, and the thing that worked for me was to use Glossary module for terms, and Glossify module for nodes.
That said, we need a single module that combines the best of all the "glossary" modules.
#4
@talatnat (#3): +1 ;-)