- Status changed to RTBC
about 1 year ago 7:46am 12 October 2023 - 🇮🇹Italy lolandese Turin, Italy
Changing status, based on the last comments above. It seems that the majority of commenters "vote" for committing this.
- 🇫🇷France louis-cuny
I would be happy to merge this issue, I totally agree we need to be able to retrieve tid that are currently wrong and broking relations
But what does happen if there is a term already existing with a tid that is going to be imported ?
We need a clarification of what is happenning in any case
- 🇮🇹Italy lolandese Turin, Italy
But what does happen if there is a term already existing with a tid that is going to be imported ?
It gets overwritten with the new data. That is exactly what you would expect when doing an operation called "Force".
- 🇫🇷France louis-cuny
I agree, we still need to make it more obvious about the differences between safe, full and force mode for taxonomies before we can merge this patch
Thanks
- Status changed to Needs work
about 1 year ago 2:11pm 26 October 2023 - 🇵🇱Poland adam_y
Not sure if a comment on Drupal 10.1 is relevant here, but I confirm that in Drupal 10.1 you can still experience an issue with inconsistency between source and destination TIDs when you expect the TIDs to be preserved from the source (what is in structure_sync.data.yml file).
It is not entirely clear to me how to achieve that goal.