Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The vocabulary in question is configured with the "Per language terms. Different terms will be allowed for each language and they can be translated." setting.
System languages are: English, Georgian, Arabic (no particular reason, just a test).
When I try to add terms to a node in Georgian, autocomplete throws errors shown on the screenshot.
The URL of the page I am on at that point:
| Comment | File | Size | Author |
|---|---|---|---|
| Picture 5.png | 55.04 KB | irakli |
Comments
Comment #1
hefox commentedDon't use the module, but looking at the code and your verison, have you tried upgrading to the dev verison?
looking at the picture it does not have this added to the description:
Comment #2
jose reyero commentedYes, to be implemented
Comment #3
miro_dietikerI'm working on this.
We have already some huge improvements.
However: the problem is in node edit form if a user changes language.
Jose, Do you have an idea how to deal with this?
Changing the node language dropdown should switch callback url (to correspond language lookup).
Also if tags are already filled out they might be in wrong language... do we need to try translating them?
Initial related issue was:
#686896: taxonomy name / help not translated
Is there something we might be able to reuse from i18nsync?
There's much more to come as soon as you're doing the first step in multilingual tag improvement.
We're trying to limit the amount of cases by predefining language and disallow language changes. But this is not generally possible..
Comment #4
jose reyero commentedNo new features for 6.x. There's some other similar issue for 7.x