Wednesday, December 11, 2024
3 changes · 17.0
Resolved issues and error corrections
This fix prevents audit trail checks from treating harmless whitespace changes in email subjects, such as line breaks, as real content changes. Businesses can send follow-up and reminder emails without encountering an audit trail error caused only by subject formatting.
Original PR description
An error can occur when the email subject contains line breaks when the audit trail is enabled.
For example, steps to reproduce using follow-up reports:
1. Add or modify the "Payment Reminder" mail template to add a line break in the subject, like {{ '\n' }
2. Install the 'account_audit_trail' module.
3. Enable audit trail in the settings
4. Attempt to send a follow-up report email to the partner
5. An error will occur: "You cannot remove parts of the audit trail.
Archive the record instead."
The issue arises because the subject is considered different from the original message, prompting Odoo to attempt an update.
New behavior:
We allow any subject whitespace modifications to be ignored whenchecking for changes in the audit trail.
opw-4317844This fixes an internal issue where the mail module used the wrong underlying process when refreshing instant messaging presence status. It helps ensure user availability information is updated reliably without changing how users interact with the system.
Original PR description
The mail module override of `_invalidate_im_status` is calling the wrong super method. This PR fixes the issue. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Webhook automation actions now always receive the expected payload field, even when a request sends an empty JSON value. This prevents crashes in automated workflows and makes webhook behavior more reliable for users.
Original PR description
- Create a web hook - In the web hook action, use the `payload` variable - Call the webhook URL with a POST request with no data The web hook crashes because the variable `payload` is undefined. The root cause comes from [1] which returns `None` in this specific case since `get_data` returns `null`. Since the `payload` is `None`, is is not included in the `eval_context`, leading to a crash. [1] https://github.com/odoo/odoo/blob/4ad762c406c942b1975060756c261444ad5a9971/odoo/http.py#L1574 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr