Closed (works as designed)
Project:
UUID Features Integration
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
30 Nov 2015 at 06:50 UTC
Updated:
18 Jun 2017 at 23:55 UTC
Jump to comment: Most recent
Comments
Comment #2
nikunjkotechaIssue was with markaspot_uuid module of mark a spot distribution.
Comment #3
mikeoharaActually, no it's not a result of Mark-A-Spot.
We use UUID Features as well, and not Mark-a-Spot and we are experiencing duplication on fra.
Comment #4
petednz commentedExperiencing this too. Having just been through a similar wrangle with node_export I found that for that issue there was a setting at admin/config/content/node_export where I could specify if i wanted matching nodes to result in updates or not
I take it this is a non-existent functionality for Terms and hence, even if Terms on both dbs have matching UUID (i copied mine over to confirm) then new Terms are created. Dang.