Anomalie #1926
fermé
Dynamic translations should not be automatically deleted when transalatable entities are updated or removed
Ajouté par Guillaume AGNIERAY il y a 7 jours.
Mis à jour il y a 5 jours.
Description
When different translatable entities use common labels, when one is updated or removed, translation are removed on all others entities.
If automatic deletion is removed, then translations should not be automatically added when transalatable entities are updated or created neither.
- Version cible
1.2.0 supprimé
I'm not sure I entirely understand what you mean (what's an "entity"?)
But I know there are several issues on dynamic translations; the main one being it's not related at all to the initial place that requires it. Currently, we can have a same string that would require several translations depending on context (check in english is a good candidate for example).
My conclusion until now is that dynamic translations are not widely used right now; so that's not a priority :)
Just not removing/updating translations will end in a very huge table; with no way to know what is used and what is not... While I'm not against a change on that part, it won't be for next major, it would require too much work.
- Assigné à
Guillaume AGNIERAY supprimé
Johan Cwiklinski a écrit (#note-2):
I'm not sure I entirely understand what you mean (what's an "entity"?)
To name them : Dynamic fields, Payments types, Contributions types and User statuses.
But I know there are several issues on dynamic translations; the main one being it's not related at all to the initial place that requires it. Currently, we can have a same string that would require several translations depending on context (check in english is a good candidate for example).
As for this particular example, in the context of payments types, bank check should be used instead of just check I think.
My conclusion until now is that dynamic translations are not widely used right now; so that's not a priority :)
Just not removing/updating translations will end in a very huge table; with no way to know what is used and what is not... While I'm not against a change on that part, it won't be for next major, it would require too much work.
:+1: I totally understand ;)
Since this is not an "anomaly" per se, but rather the way it is supposed to work at the moment, I think this issue can be rejected (I cannot set this status myself) ;)
If necessary, an "evolution" request will be opened later to improve the current implementation of dynamic translations.
- Statut changé de Nouveau à Rejeté
I've opened the evolution ticket so the idea will not be lost ;)
Formats disponibles : Atom
PDF
Mis à jour par 
Mis à jour par