diff options
| author | qsm-odoo <qsm@odoo.com> | 2020-12-28 11:31:36 +0000 |
|---|---|---|
| committer | qsm-odoo <qsm@odoo.com> | 2020-12-28 11:31:36 +0000 |
| commit | 8af75e00bdcda3d5ff4facd2f5f146e1d6bf79e4 (patch) | |
| tree | aead95ab42ec567b29b0c046b3f4fd2f36448a6e /addons/auth_signup/controllers | |
| parent | 74453020c89facd504c140023e302a72ae6b415e (diff) | |
[FIX] web_editor: allow mass mailing users to access the editor
Mass mailing users with low access rights were not able to access the
editor anymore if the website application was not installed (or any
other app giving ir.ui.view read access rights to the related users).
This commit fixes the problem but should be handled another way in a
future master refactoring. The problem was that the views are now
private by default: they can be read thanks to read_template provided
they declare a group that the user has and that the user has read access
rights.
For the case 'read_template web_editor.colorpicker', it works for
website editor users as the view has the base.group_user group
*and they have access rights thanks to publisher/designer groups*.
For mass mailing users, no such group exists though so they simply
do not have the rights to read that template anymore. Seems safer
to force it for this template only while waiting for a better
access rights refactoring.
Note: using 'render_public_asset' which allows to bypass rights if
the user has the group the view requires was also a solution.
However, that would turn the 'read' into a 'render', which is
a less stable change.
task-2412544
closes odoo/odoo#63832
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Diffstat (limited to 'addons/auth_signup/controllers')
0 files changed, 0 insertions, 0 deletions
