Daily updates from Odoo
Friday, April 4, 2025
8 changes
1 change
Resolved issues and error corrections
The VoIP module now avoids asking for a field that can already be determined automatically. This reduces friction for related workflows and makes testing or dependent customizations easier without changing the core user experience.
Original PR description
This is highly annoying for tests and dependant modules, while this field is used in 3 flows and can be easily deduced.
7 changes
Resolved issues and error corrections
This update removes an unnecessary warning shown when postponing replenishment rules created by the superuser. It reduces confusion for inventory users while preserving the corrected behavior from a previous fix.
Original PR description
Thanks to this fix: https://github.com/odoo/odoo/commit/8ad00b8ee6340dba1e027bb27a8f05489b4253a9 we can revert this one: https://github.com/odoo/odoo/pull/200777/commits/237feaee5fcf1e166bf39e78e8839b191f92c306 The pot file already deleted: https://github.com/odoo/odoo/commit/0361582de7c28bb4847a9c4dbaa712b67f4ca577#diff-4424c1629e21b466bb7af6ab0cb3a674d1bf3e75d93e7e76cf77870dc5bcc853R8693-L9114 opw-4628611
Odoo now safely ignores translation-control markers in web view templates during browser-side compilation. This prevents form and kanban views from failing when those markers are present, improving reliability without changing what users see.
Original PR description
Form and kanban view archs are compiled into owl templates. Those archs are translated server-side, before being sent to the client. They can contain `t-translation` directives (typically ="off" to…
Form and kanban view archs are compiled into owl templates. Those archs are translated server-side, before being sent to the client. They can contain `t-translation` directives (typically ="off" to disable translations). This tells the view processing in python not to translate the subtree. In the js compilers, that attribute is listed among the tolerated attributes for kanban archs, but not for forms. However, the cases are similar, so their should be not differences between the two. Moreover, since [1], compiled templates are wrapped into a ```xml <t t-translation="off"/> ``` node, s.t. terms aren't translated twice (once in python, and once in js, by owl). Instead of tolerating the `t-translation` directive in form view, this commit ignores it in all view compilers. This directive indeed makes sense, so it is valid to use it in kanban and form archs (then used by the view processing in python). But the view compilers in js must ignore it, so we simply remove it. [1] odoo/odoo#158759 Fixes runbot error-134670 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
The editor now correctly enables AI and translation actions when users select normal text, even if the surrounding content includes protected elements such as a signature. This prevents valid selections in the email composer from being blocked unnecessarily.
Original PR description
**Problem**: If the selection does not include unsplittable nodes but the `commonAncestorContainer` contains one, the AI/Translation button will be disabled. **Solution**: Instead of relying on `commonAncestorContainer`, check only the traversed nodes to determine if the selection is valid. **Steps to reproduce**: 1. Open Full Composer with a signature. 2. Add text. 3. Select only the text you added. - **Issue**: The AI/Translation button is disabled. **opw-4649819** --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
PayPal payment requests now leave out the company email field when no email is set, instead of sending an empty value that PayPal rejects. This helps avoid confusing payment integration failures for businesses with incomplete company contact details.
Original PR description
Since paypal does not allow empty fields to be sent, its better to add email only if it exists. Some customers find it confusing that paypal integration fails without proper feedback that the issue comes from the empty email in their company form. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents accounting tax updates from failing when expected repartition line details are absent. Instead of triggering an error, the system now skips that update safely, improving stability for affected accounting configurations.
Original PR description
When there are no repartition_lines we should skip updating them because it will cause IndexError: list index out of range. 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
The Gantt view compiler now safely accepts older translation markers while ignoring them during processing. This prevents unnecessary errors and keeps behavior aligned with the broader platform change, with no expected visible impact for users.
Original PR description
This commit is the counterpart of odoo/odoo#204833 which ignores the `t-translation` attributes in view compilers. As a consequence, this directive should no longer be in the list of accepted directives.
This update corrects an automated website shop test for subscription product variants. It helps ensure the checkout flow for variant-based subscription products is reliably validated, reducing the chance of unnoticed issues reaching users.
Original PR description
Fixing the tour that has been introduce here https://github.com/odoo/enterprise/pull/75658/commits/c2d18cea5db278b5a3203c4d3646411fc9bbd450 runbot-110627