Moving a term ends up with the term with several parents (same name)
| Project: | Taxonomy Manager |
| Version: | 5.x-1.1 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Hello! Nice module!
This is an issue which can be easily reproduced.
Create a taxonomy with the following terms:
Spain, Catalonia, Barcelona, Mexico, Barcelona
and with this hierarchy:
Spain ->Catalonia -> Barcelona
Mexico -> Barcelona
Note that Barcelona and Barcelona are different terms!! (different tid).
Now you create a new term called "Main Street" and it goes direct to the root.
Now, click on it and click "Move". The autocomplete field that appears to be used to find the parent will only display one Barcelona if you type "bar...".
Select it, and click "Move" and the term will be below both "Barcelona"s, so it's going to have multiple parents (which is not the desired result).
What could be useful is:
1. display the parents of the term while searching for whatever (this needs quite a lot of code I think).
2. display the tid together with the term: that would display 2 different results for "bar" -> Barcelona (tid:4) and Barcelona (tid:6) for example...
3. Just display Barcelona twice and the user might select the good one or the bad one. That is the worst solution, but at least will allow an admin to move a term and not end up with a duplication/ multiple hierarchy.
Any solution??
Thanks
#1
I had the same problem with some of my vocabularies. To solve it, I was temporarily renaming one term, e.g. _Barcelona. This is of course very inconvenient.
At the moment I see point 2 as the "best" solution, maybe I find time to implement it. In my point of view, the best thing would be to have a double tree window interface (the tree with the same voc on the page twice), where you can move the terms from one tree to the other.
#2
But a double tree view can bring some extra jquery and other problems...
Yes, please, add the tid and then the terms will be moved to a single location (not 2 or more).
The problem with renaming one term is that, normally, we can't know if there are other terms or not with that same name. Of course we should know where is the "new parent" located, so we can change that name and move the terms to "_bar" for example. But always changing the future parent name to have a _ in the front is not the best option.
It would be better to display all terms, even without the tid, so one might think the system is showing terms twice but it's not.
well, if you could have a look at the code and implement some of these functionalities, that would be great!
Thanks!