Im trying to adapt the glossary mode (based on the glossary example view) to the taxonomy_term view using an attachment display.
Glad for any tips from anybody who has successfully achieved an alphabetical pager at the top of the emulated taxonomy term view (and if I succeed in the meantime I'll post my experience here).
Thanks, Webel
Comments
Comment #1
webel commentedComment #2
merlinofchaos commentedUnfortunately, the taxonomy argument isn't just a raw string so it doesn't support the length property which is what the glossary uses to turn the string into a letter.
You *might* be able to achieve this by adding the 'related terms' relationship, and then adding the "Taxonomy: Term" field and setting it on the relationship. Except I just looked and this version of the field also does not support changing the length.
So at this point this would not be doable without applying a custom argument handler to taxonomy terms to make that work.
Comment #3
webel commentedThanks very much for the concrete feedback, it save me time fumbling and futzing and guessing. The feature is however a very natural request and one that interests my client (who is now probably enticed by the successful demonstration of a nodes glossary), so I remain grateful for any further feedback from anybody.
On a related matter that may provide a solution, I am looking for ways to link a custom node type Definition to a matching term in a vocabulary called Keywords.
Every Definition (which unlike a taxonomy term has support for field and rich definition text etc.) should be tagged by at least one matching term from the vocabulary called Keywords, and possibly also many others.
(Then I could create a node-based glossary targeting Definition type).
I am familiar with the Category project, which is node-based, not term based, but it is a huge step to change to that now. In the meantime I am looking for a simple way to bind taxonomy terms with matching nodes, so I have the best of both worlds, and can also deliver the alphabetical glossary my client wants (he is already naturally confused about the difference between terms and nodes).
I realise this is beyond the scope of Views, however perhaps somebody here can help, as in the end it has to pass through views and the glossary approach to work.
And I am familiar with the Glossary and Glossary2 projects, neither of which seem to be able to replace the rich Definition custom node type I've developed.
Comment #4
Countzero commentedI'm unfortunately unable to help at this time, but wanted to thank people in this thread for confirming the glossary mode doesn't work with term views.
In fact, it does, but I can't get the alphabet displayed on my page.
Comment #5
merlinofchaos commentedChanging this to a feature request.
Comment #6
webel commented@merlinofchaos Thanks for continued interest in this possible feature.
Comment #7
esmerel commentedComment #8
merlinofchaos commentedI'm pretty sure this exists now, or what exists now is the best that will happen.
Comment #9
Grayside commentedYes.