summaryrefslogtreecommitdiff
path: root/addons/barcodes
diff options
context:
space:
mode:
authorLucas Perais (lpe) <lpe@odoo.com>2019-03-08 12:57:02 +0000
committerLucas Perais (lpe) <lpe@odoo.com>2019-03-08 13:30:30 +0000
commit6b676f62352ca133723bf9cc9bafa8d05728eb0e (patch)
tree26537a892b05533db89e65ad687027b70dbf4ba6 /addons/barcodes
parent4524dcd69158763575124e5867a7e1d295ebe034 (diff)
[FIX] web: record datapoint context without group_by or orderedBy
Have a list view, apply a group_by and a filter with a sort parameter Click on one record to access the form view Have a x2m within it Before this commit, the x2m records were loaded with a context containing the keys orderedBy and group_by It seems harmless at first, but even conceptually those keys should not be here - they apply on a list of records, and not to individual ones - they may contain field names not existing in the x2m model Hence, when accessing another list view through an action button, the list will try to be orderedBy or group_by with the given context Which is plain wrong in the first place and may cause crashes After this commit, the context of a record datapoint (representing a single record) is stripped from the keys Read the opw for a concrete use case OPW 1943583 closes odoo/odoo#31706 Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>
Diffstat (limited to 'addons/barcodes')
0 files changed, 0 insertions, 0 deletions