Active
Project:
Taxonomy Lineage
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
25 Nov 2011 at 10:50 UTC
Updated:
5 Sep 2012 at 08:51 UTC
Jump to comment: Most recent file
Comments
Comment #1
chinita7 commentedI just found out that "Strip weights" setting can remove the term ids. However All the terms (including the deepest terms) are still having duplicated terms as their child terms.
What I would like to do is
but not
Comment #2
xjmYou probably want to add two fields to your view: the term name, and the term hierarchy. Exclude the hierarchy from display. You might also want to add the term depth field, exclude that from display as well, and use it to provide indentation formatting.
Comment #3
chinita7 commentedThanks I tried both fields "Taxonomy: Term" and "Taxonomy: Hierarchy" and excluded "Taxonomy: Hierarchy" using " Lineage nested list" style with "Nesting Field:hierachy". Then the duplicated parent terms were removed but the duplicated child terms are still there as their grand child terms (one more level down). I also tried "depth term" and excluded it but I really could see the deference unfortunately. Now it's looking like this.
Comment #5
timtunbridge commentedIs it OK to reopen this again, forgive me if this is not the right etiquette.
I am experiencing a similar issue, namely duplicate entries appearing in the tree. Immediately after each h1 h2 h3 etc the same value as contained in the header tag is repeated in a ul li div span. Every value in the tree is being repeated in this way.
Screenshot1 shows the underlying taxonomy hierarchy. Screenshot 2 the view and Screenshot 3 the results.
Following #2 above, Taxonomy Hierarchy is excluded from the display (with strip weights also selected). Taxonomy Term is being displayed.
The duplicates have a CSS class of views-field-name so I could target these with a display: none, but am I just doing something wrong?
Thanks for clarifying.
Comment #6
Vilcoyote commentedI have the same issue, has anyone ended up solving the issue?
Comment #6.0
Vilcoyote commentedbetter discription