diff options
| author | Aaron Bohy <aab@odoo.com> | 2016-05-18 09:22:35 +0200 |
|---|---|---|
| committer | Aaron Bohy <aab@odoo.com> | 2016-05-18 09:39:17 +0200 |
| commit | 1bab8eb1457a624ecd0f3c03d05efa8c729f2882 (patch) | |
| tree | cb85cf801b129dc4c250d4bd0bb1216d4a9b3e40 /addons/website/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js | |
| parent | e80c2bd17e2ba7e8ed1fbd40696045283efe301d (diff) | |
[FIX] web: form_view: new record and FieldBinaryImage
Form views with a FieldBinaryImage produced a traceback (only visible in the
server-side logs) when creating a new record from an existing one, because the
fields were re-rendered before being updated (in this case reset to their
defaults). In the case of the FieldBinaryImage, as the field wasn't reset yet,
we tried to load the image of a null id, which produced the traceback.
This rev. ensures that the fields are updated before being re-rendered when
switching to another (possibly new) record.
Note: this is spaghetti code, several re-rendering are triggered when switching
between records (e.g., when updating the fields value, when actualizing form
view mode). This should definitely be refactored/simplified.
Diffstat (limited to 'addons/website/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js')
0 files changed, 0 insertions, 0 deletions
