odoo/odoo#73237
Created by fw-bot
Merged
at 37e9dda232cff05278baf829b4ffbd6946d64627
Statuses:
- legal/cla: Contributor License Agreement check
- ci/runbot: Odoo Test Suite
- ci/upgrade_enterprise: Test upgrades for enterprise master
- ci/style: Optional style check. Ignore it only if strictly necessary.
- ci/security: Required security check. Can only be ignored by security team.
- label
- odoo-dev:master-12.0-fix_missing_digest_user_invite-pmo-Y4DF-fw
- head
- f97d8400cbadc8a98cc177e39d19fb2790c40fdc
- merged
- 5 years ago by Platform, Paul Morelle (pmo)
| odoo/odoo | |
|---|---|
| 12.0 | #73077 |
| saas-12.3 | #73154 |
| 13.0 | #73158 |
| 14.0 | #73165 |
| saas-14.3 | #73224 |
| saas-14.4 | #73231 |
| 16.0 | |
| 17.0 | |
| 18.0 | |
| saas-18.3 | |
| saas-18.4 | |
| 19.0 | |
| saas-19.1 | |
| saas-19.2 | |
| saas-19.3 | |
| saas-19.4 | |
| master | #73237 |
[FW][FIX] digest: avoid exception on user creation
Scenario to reproduce the issue on runbot 12.0 Community:
- Go to Settings > Technical > Email > Digest Emails
- Select the Weekly Digest
- Click on Action > Delete
- Click on OK
- Go to Settings > Users & Companies > Users
- Click on Create
- Fill the Name and the Email Address
- Save
- Odoo Server Error - Missing Record
Some users seem to delete this record to stop receiving the digest for everyone, including for future users. The problem is that, even if the digest has been deleted, the config parameters are still referencing it.
This commit prevents the exception by having an empty recordset if the digest does not exist.