diff options
| author | Martin Trigaux <mat@odoo.com> | 2019-09-17 15:17:04 +0000 |
|---|---|---|
| committer | Martin Trigaux <mat@odoo.com> | 2019-09-18 14:56:41 +0000 |
| commit | 543a5523a30c993f60eba3c6d56d54dea2857eb3 (patch) | |
| tree | d9486165ddbeac7c2ddae868ee527f9d7456e927 /addons/web/static/src/js/fields/basic_fields.js | |
| parent | 2425c7b223398fa2bc43ecbb95111be15e1599ce (diff) | |
[FIMP] base: remove all translations when writing False
This "bugprovement" resolve the old issue of writing on a translatable
field a falsy value.
Before this commit, only the translation value was removed. When no
translation is present (or when the value is not set), the value is
retrieved directly from the source field.
Before 18d9c2cab2426, it was still possible to go around this issue by
removing manually all ir.translation entries and writing with a user
in en_US.
This is no longer possible as writing on a translatable field always
uses translations when in multi-language environment, without
exception of en_US.
When writing a falsy value on a field, the expected behaviour is to
reset the value and see that falsy value after saving, not the old
value stored on the source model.
Remove all translations and force to update the column.
Removing one individual translation is still possible in the
translation popup.
Task id: 2062415
closes odoo/odoo#37077
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
Diffstat (limited to 'addons/web/static/src/js/fields/basic_fields.js')
0 files changed, 0 insertions, 0 deletions
