- last update
over 1 year ago 55 pass I was running into an issue with #9, when selecting more than one term to merge into a new term, duplicate new terms where being created.
Looking at the check to see if a term exists it looks like it's calling "free_tagging" as the vid to check. Changing that check to look at the vocabulary id seems to fix that. With the vocabulary id in the check it also will check if the term typed into the new input box already exists and do just the regular merge into the existing term.
Long time lurker here, first time poster, so hopefully I did this correctly!
Improving the way I called vocabulary id - moved it to a hidden field on the form.
- First commit to issue fork.
- πͺπΈSpain aleix
Hi, I just created a MR ... It's about the same thing but is done using the core Actions API with a derivative that could be executed from any view. So I think it's easier because with any terms view it could be called.
It may be used this in a new view with `/admin/structure/taxonomy/manage/%taxonomy_vocabulary/merge_terms` path that is restricted to a one defined vocabulary.