Closed (outdated)
Project:
Feeds
Version:
7.x-2.x-dev
Component:
Feeds Import (feature)
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Oct 2013 at 13:47 UTC
Updated:
9 Feb 2026 at 18:57 UTC
Jump to comment: Most recent
Comments
Comment #1
vegansupreme commentedI have the same problem.
As a fix, using the 7.x-1.x-dev version of Term Merge Works the best because it auto detects duplicates. There's still a lot of clicking if you have a lot of terms though.
Comment #2
summit commentedHi,
@vegansupreme I have exactly the same strategy as you but off course this is not a fix, but a labor intensive work around. The good part that the module builder of term merge has build in some great stuff from my needs, but still it is a work around and not a real fix..
Does anyone experience the same problem and have a real fix?
Greetings, Martijn
Greetings and thanks in advance for your reply!
Comment #3
vegansupreme commentedSummit, you're absolutely right, it's not a fix. I meant to edit my post but figured it was too late. I just wanted to recommend the 1.x-dev branch of term merge. Last I checked, the 2.x branch wasn't working for me, at least the duplicate merge feature wasn't working correctly.
Back to finding a real fix: I've been using Feeds off and on for quite a while, and I'm sure this problem wasn't happening a few months ago. Maybe try Alpha6 or 7.
Comment #4
vegansupreme commentedI think I've found a much better work around! VBO has a similar (identical?) issue:
#1507216: Adding new terms to nodes using autocomplete widget creates duplicate entries in vocabulary
I used the code in #7 to make a custom module, and poof! Feeds no longer creates duplicate terms! See also
#1812794: Prevent storing duplicat references
In this issue, there's a patch for VBO that may or may not work for feeds. I've not tried it on feeds. The custom module work around worked for me.
--EDIT: This might not actually be working! Will update again soon, when I confirm.
--EDIT: It DOES seem to be working. I may have just used incorrect import/tamper settings.
Comment #5
shaneonabike commentedWhat exactly do you mean you put that into a custom module? Is it that you wrote code that you forced tamper to use? If so what exactly did you do...
Comment #6
bluegeek9 commentedDrupal 7 reached end of life and the D7 version of Feeds is no longer being developed. To keep the issue queue focused on supported versions, we’re closing older D7 issues.
If you still have questions about using Feeds on Drupal 7, feel free to ask. While we won’t fix D7 bugs anymore, we’re happy to offer guidance to help you move forward. You can do so by opening (or reopening) a D7 issue, or by reaching out in the #feeds channel on Drupal Slack.
If this issue is still relevant for Drupal 10+, please open a follow-up issue or merge request with proposed changes. Contributions are always welcome!