Closed (fixed)
Project:
Taxonomy Manager
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
20 Dec 2007 at 18:16 UTC
Updated:
29 Dec 2022 at 23:28 UTC
Jump to comment: Most recent
Comments
Comment #1
wim leersThis isn't and can't ever be a HS issue. HS merely displays taxonomy terms, it does never affect the term-nodes relations, you can simply use it to change those.
You've clearly given the cause yourself: the Taxonomy Manager module.
Comment #2
mh86 commentedhi!
can you explain me exactly which terms you merged? it's not possible to have duplicated entries in the term_node table, so I'm a bit confused how this can happen...
you can add a node distinct filter to your view. this will prevent showing the same nodes more often, but won't solve the problem itself.
another reason may be, that your view is not correct.
Comment #3
Anonymous (not verified) commentedFor example, I had a hierarchical category 2007->Ruby->February that I merged with a category 2007->February. Once I did that the view started showing duplicate nodes. The duplication only happens once I apply the category filter to the view. The original view does not have duplicate entries.
The node distinct filter does fix the display, but I'm still interested in how to fix the real problem.
Comment #4
jefbak2 commentedI had to uncheck the "TYPE" entries in my volcabulary to stop duplicate fields from showing up during content creation and views. I might have just missed this necessity in the install.txt however...
Comment #5
mh86 commenteddoes this problem still exists? this problem might be more related in configuring the views than a problem in merging
Comment #6
wim leersClosing due to lack of response.