The breadcrumb that will show up when displaying a node in full view now depends on which of the attributed terms are closer to A in the alphabet.
This is a bit arbitrary, it would be better if the node breadcrumb was based on vocabulary weight.
It is possible to get to a certain node from many directions if it has been ascribed more than one term, but by allowing the weight system to influence which breadcrumb will actually be displayed when you have finally arrived at the node and displayed it in its full length - would be really great!
Consider the following example:
We have three vocabularies: Language, Topic and Type
Each vocabulary contains a number of terms; eg.
Danish, English and German for Language
Pollution, Crime and Taxes for Topic
Article, Petition and Essay for Type
As it works now, if any node is assigned one term from each vocabulary the final breadcrumb shown when displaying the full view node will simply depend on which term is alphabetically closer to A.
But by using the weight system it would be possible to decide which vocabulary the breadcrumb should follow in full view mode.
I hope I have made myself clear.
Best Regards and thanks for a great module,
Lennart
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | vocabulary_weight_based_breadcrumb.patch | 661 bytes | iferrer |
Comments
Comment #1
nedjoIt's a good suggestion, I'll look into this if I get a chance--or if anyone wants to submit a patch, pls do.
Comment #2
lennart commentedI should note that it is already possible to do this now - indirectly. It just requires a bit more work, because it has to be done at the term level.
For example setting all terms individually in vocabulary 'topic' to a lesser weight than all terms in vocabulary 'type' will make the breadcrumb follow 'topic'. From a usability point of view it would be even better if the breadcrumb would follow weight of vocabulary first, and only the weight of terms when those are unequal.
Best Regards,
Lennart
Comment #3
eferraiuolo commentedBetter yet it breadcrumbs should be generated like they are suppost to be! Bredcrumbs are your trail through a website, so if you got to a node through one path your breadcrumbs should reflect it, but if you came to the same node through another navigation path then your breadcrumbs should reflect that path.
I am having a problem with this and if breadcrumbs for taxonomy_context worked like real breadcrumbs my problem would not be an issue!
Comment #4
iferrer commentedHere is the patch to get this feature, but the module to be patched is taxonomy.module, not taxonomy_context.module.
Comment #5
nancydruReopen this with a current release if it is still valid.