Monday, March 23, 2026
6 changes · 17.0
Resolved issues and error corrections
This update prevents the entire report cron process from stopping if a single report export fails. Now, the cron will continue to attempt exporting other reports, ensuring timely delivery of all necessary reports. This improves reliability and reduces potential data delays.
Original PR description
If an error is raised during the export of reports cron execution, the whole cron stops due to the fact that the error is never catched This commit will ensure that even if there is an error with one of the report export, the cron won't top and will try to send to other documents task-5469038
This update fixes an issue where currency rates were incorrectly calculated after Bulgaria transitioned to the Euro. The system was using reversed rates from the XML data, leading to inaccurate unit conversions. The fix ensures accurate currency calculations by using the correct 'RATE' value from the XML.
Original PR description
Issue: after Bulgaria switched to EUR, currency rate fetching from BNB was incorrectly set to still use reversed currency rates from the fetched XML, resulting in unit-to-EUR and EUR-to-unit rates being flipped in the database. Solution: adjusting the parser to get rate from 'RATE' rather than 'REVERSERATE', as the XML provides both. task-6050519
This update resolves a minor issue with a message displayed in the HR payroll documents. The fix ensures accurate and consistent reporting, preventing potential confusion or errors in payroll processing. This change improves the reliability of the documents generated for employees.
Original PR description
Task#5980045
This update resolves a problem where strict email servers rejected Odoo emails due to improperly folded subject headers. By preventing folding and adhering to RFC standards, Odoo ensures compatibility with a wider range of email systems, improving email delivery reliability. This change aligns with best practices for email communication.
Original PR description
…r rejections Yahoo and other strict mail servers reject emails with folded Subject headers containing RFC 2047 encoded-words when the folding occurs at inappropriate positions, resulting in "554…
…r rejections Yahoo and other strict mail servers reject emails with folded Subject headers containing RFC 2047 encoded-words when the folding occurs at inappropriate positions, resulting in "554 Invalid Subject header" errors. The root cause is in Python's stdlib (bpo-144156). In an ideal world we would be fixing the issue there, but experience tells us that they are very slow to fix bugs / merge PRs in the email module, and even when they do they usually don't backport the fixes in the python versions we use. This commit extends the existing IdentificationFieldsNoFoldPolicy to also prevent Subject header folding, keeping long subjects on a single line (up to 998 characters per RFC 5322 "MUST" requirement, from the 98 "SHOULD" limit). Since at it, include the other "user defined" smtp headers: to, from, ... The solution follows the same pattern already established for identification headers (Message-ID, In-Reply-To, References) where Odoo prevents folding to avoid MTAs rewriting these critical headers and breaking email threading. closes odoo/odoo#250388 See-also: #243119 Backport: #247057
This update fixes a potential issue where users could inadvertently create incorrect group-view relationships in Odoo. The change prevents assigning inherited views to groups directly, simplifying configuration and avoiding upgrade-related errors. This ensures data integrity and a smoother user experience.
Original PR description
**Steps to Reproduce:** - Create a new database. - Install any module (for example, Payroll). - Go to Settings → Technical → Security → Groups. - Open any group and assign an inherited view in the…
**Steps to Reproduce:** - Create a new database. - Install any module (for example, Payroll). - Go to Settings → Technical → Security → Groups. - Open any group and assign an inherited view in the Views section. - Upgrade the module. **Issue:** - Odoo already prevents assigning groups directly on inherited view records in ir.ui.view. However, it is still possible to indirectly assign groups to inherited views through res.groups via the view_access relation. - This creates entries in ir_ui_view_group_rel and can trigger a ValidationError during module upgrades. As a result, users may unknowingly create invalid group-view relations, leading to errors and confusion. **Solution:** - Add a validation constraint on res.groups to prevent linking groups to inherited views via the view_access relation. - Raise a ValidationError when such an assignment is attempted, with the message: "Groups should instead be defined using the 'groups' attribute inside the view XML definition." This ensures that inherited views cannot be assigned to groups, avoiding invalid configurations and preventing errors during module upgrades. **opw-6015526** --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes a problem where users received an incorrect error message when testing their outgoing mail server connection. The change ensures users see the correct error message, improving the overall user experience and preventing confusion. This resolves a minor usability issue.
Original PR description
Current behavior before PR: Wrong error message when clicking the button Test Connection of Outgoing MailServer. Desired behavior after PR is merged: Correct error message. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr