- 🇦🇺Australia VladimirAus Brisbane, Australia
Thank you for contribution. 👍
Drupal 7 is no longer supported. 🤷♂️
Closing as outdated. 🔐
Hi
Here is one common parent-child vocabulary with i18n translation enabled usecase.
When child term in default language is edited and it's translations are added - created translations are all placed in root level.
It would be very handy if parent translations could be checked and if they exists translated terms are placed automaticaly as childs of translated parents. And if parent translations do not exist created translated terms can be placed in root level as default.
I believe this is not a simple task... but such a functionality would make Taxonomy Manager module a geniune tool for i18n translation enabled vocabularies with tree structure!
Currently, such vocabularies are painfull to create with a lot of manual work. All child translations have to be moved to respective parent translations manually which is a lot of hard work. And there are also some active issues which makes it even harder:
https://www.drupal.org/node/2461381 →
https://www.drupal.org/node/2461085 →
Closed: outdated
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Thank you for contribution. 👍
Drupal 7 is no longer supported. 🤷♂️
Closing as outdated. 🔐