Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Hi there,
I would like to report what I suppose to be a bug.
I created a taxonomy of type "translate", when I create the first term (in french) and then click on "save and translate" the term is created and I arrive on the translation page.
If I use the "translate" action link in the top table to translate my term, the term is created, the translation set is created but an empty translation set is created too.
If I use the autocomplete field in the bottom to translate it, the term and the translation set are created and there is no empty translation set created.
the second behavior seems normal to me because I do not understand the usefulness of an empty translation set.
Let me know if I make a mistake.
| Comment | File | Size | Author |
|---|---|---|---|
| Capture_i18n_taxonomy.jpg | 79.14 KB | alexdezark |
Comments
Comment #1
alexdezark CreditAttribution: alexdezark commentedComment #2
alexdezark CreditAttribution: alexdezark commentedComment #3
alexdezark CreditAttribution: alexdezark commentedNo one is interested in this?
Is it or is not it a bug?
Should I explain to the end user that for translating the term he musn't use the button marked "translate"?
Comment #4
suffering drupal CreditAttribution: suffering drupal commentedHi, I have just installed i18n_taxonomy and tried a bit.
I looked for the first time at the "translation set" page and discovered several "undefined" taxonomy terms in the list.
The problem is I made a mess myself with the taxonomies. I tried to convert an old existing Taxonomy term "Categories" (which already had independent translations AND term ID (number) in NL, IT and ES) into a new Taxonomy term "Categories-def" (tryout name). So can't tell if the undefined terms are created by myself or by i18n_taxonomy...
What I wanted to achieve is: to use only the Default language Taxonomy Term & ID and have translation be done by Field Translation and i18n_taxonomy so that you have the right word for the translated Terms, but still only ONE Term ID for all the languages (only ONE term in the list and only ONE core path for all the languages; /taxonomy/term/## with path translation for the aliases in the different languages).
Is that actually possible? Important question!
I thought it should be possible with i18n-taxonomy
There are two reasons why I want to achieve this:
1 - not have such a long list because of each taxonomy term in all the languages (I intend to use about 15 languages)
2 - have taxonomy syncronized automatically when you make translations of nodes. Syncronization does happen with the 'old' way of translating (the normal i18n) but NOT with field translation. Just imagine: if you have a page with 4 different Vocabularies that you want to translate 15 times. You go crazy just remembering and setting the taxonomy again and again with each new page.
I should try again with a fresh install make sure where the problem comes from, but I have now spent so many years just doing fresh installs and tryouts, without ever really finishing a website, that I don't know if I will have the energy to do it again.
Anyway, for now I'm going to bed, two hours late (again)
Tomorrow I'll have a look to understand what you mean by "Should I explain to the end user that for translating the term he musn't use the button marked "translate"?" it sounds rather enigmatic ;)