Uwazi: Properties of type 'select' are not recognising translated list/thesaurus items
The list/thesaurus on this Uwazi instance has been translated into AR:
...but when you are in the AR interface, the items are in English:
...but the properties of type "multiselect" seems to pulling in the translated list items, as expected.
kjantin
All 8 comments
Another partner has reported the same problem on their Uwazi instance that uses AR translations.
kjantin
on 5 Mar 2020
The problems with the translations were there due to two things:
- Sometimes the context id was not passed properly to the translations module
- The translations module accepts void context ids without throwing any exceptions
The code is going to be changed to throw exceptions when a translation is requested without context id.
This happened in two places in the code, in the metadataformfield the context id was template._id and as this object is an immutable the correct way to get the field is with template.get('_id').
The second bad translation occurred when multiple entities from different templates were selected, no context id existed to process the translations.
gabriel-piles
on 13 Mar 2020
A separate issue about the missing translation when multiple items with different templates are edited was opened #2820 , and it is not going to be solved in this fix.
gabriel-piles
on 16 Mar 2020
Hi @konzz and @gabriel-piles - was this issue supposed to have been fixed and deployed with this latest deployment today? Unfortunately, the original issue of the properties of type "select" (and I think also "multiselect" now) are still not displaying the proper translated values.
kjantin
on 30 Mar 2020
@gabriel-piles select translations are not working for me either. Multi-selects are working though. @kjantin can you provide an example of multi-selects not being translated?
txau
on 30 Mar 2020
@kjantin can you provide an example of multi-selects not being translated?
Yes, I have shared an example privately.
kjantin
on 30 Mar 2020
Hi @kjantin, the changes about the Select translations have not been deployed yet, but the functionality is implemented and working in the code for the next deploy.
gabriel-piles
on 31 Mar 2020
Fixed.
txau
on 31 Mar 2020
Related issues
fititnt
路
5Comments
RafaPolit
路
3Comments
HSips
路
8Comments
RafaPolit
路
6Comments
danicatalan
路
7Comments
Most helpful comment
The problems with the translations were there due to two things:
The code is going to be changed to throw exceptions when a translation is requested without context id.
This happened in two places in the code, in the metadataformfield the context id was template._id and as this object is an immutable the correct way to get the field is with template.get('_id').
The second bad translation occurred when multiple entities from different templates were selected, no context id existed to process the translations.