Copy() behaves wrongly with translations when object has O2M relations with translatable fields.
Bug #524424 reported by
Numérigraphe
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) |
Fix Released
|
Medium
|
Unassigned | ||
5.0 |
Invalid
|
Undecided
|
Jay Vora (Serpent Consulting Services) |
Bug Description
in the current 5.0, when you use a language other than English and copy a stock location with children, the names are wrong:
- the parent's English name is ok but the translated name is that of the last child
- the children's translated names are ok but the English names are replaced with the translated names.
Lionel
Changed in openobject-addons: | |
assignee: | nobody → JMA(Open ERP) (jma-openerp) |
Changed in openobject-addons: | |
status: | New → Confirmed |
affects: | openobject-addons → openobject-server |
Changed in openobject-server: | |
milestone: | none → 5.0.9 |
summary: |
- Wrong name when duplicating stock location + Copy() behaves wrongly with translations when object has parent-child + relations with itself. |
description: | updated |
summary: |
- Copy() behaves wrongly with translations when object has parent-child - relations with itself. + Copy() behaves wrongly with translations when object has O2M relations + with translatable fields. |
Changed in openobject-server: | |
milestone: | 5.0.9 → 5.0.10 |
Changed in openobject-server: | |
milestone: | 5.0.10 → 5.0.11 |
Changed in openobject-server: | |
milestone: | 5.0.11 → 5.0.12 |
Changed in openobject-server: | |
importance: | Undecided → Medium |
To post a comment you must log in.
Hello Lionel,
Here is the patch that helps the user go in the proper direction.
Would you please apply and check?
Till then, I am working on more suitable one.
Thanks.