diff options
| author | jem-odoo <jem@openerp.com> | 2018-06-06 10:47:48 +0200 |
|---|---|---|
| committer | jem-odoo <jem@openerp.com> | 2018-06-07 16:52:00 +0200 |
| commit | a7d9d966a5d3bca32fd8585661f0c88a6464b957 (patch) | |
| tree | c3e8d340b0c7653ed9f4d1c99630b7f93bcbdc57 /doc/reference/javascript_reference.rst | |
| parent | f6a74f40b5c781870f7dc15bc125f879c73e27ad (diff) | |
[FIX] models: m2o display name as sudo in read_group
In 10.0, the resolution of the m2o field in a read group was
done with a `read` (which sudo the name_get). So, the access
rights were bypassed to get the display_name of the related
records.
In 11.0, a call to `name_get` but not as `sudo` causing access
error in some case. For instance;
- a user has read access on project
- he log some timesheets
- its access to project is removed, but not the timesheet ones
- trying to access its own timesheet via the grid view (which does
a read_group)
- the user gets the access error for project.
The read_group should reproduce the behavior of the `read` method,
so the `name_get` for m2o field during a read_group is now sudoed
to restore previous behavior.
opw-1855942
Diffstat (limited to 'doc/reference/javascript_reference.rst')
0 files changed, 0 insertions, 0 deletions
