Monday, February 10, 2025
9 changes · 17.0
Resolved issues and error corrections
Receipts for account settlements and other non-editable orders no longer show the misleading prompt to start adding products. This avoids confusing cashiers and customers when an order correctly has no product lines.
Original PR description
Issue: When settling user account, the order will not have any order lines, that will display a misleading empty state on the receipt, saying: "Start adding products". Fix: We do not display this empty state, when the order is not editable, which is the case of, but not only, settling an account. Note that we have another related PR https://github.com/odoo/enterprise/pull/76370 for the same ticket, which fixes only the case of settling an account. However, @adgu-odoo suggested to make the fix more general, to fix the case of not only settling an account, but also other possible cases where we show the OrderWidget in a receipt. If this PR is merged, the other one should be closed, and vice versa. opw-4430325
This fix updates phone number links to use the standard format expected by browsers. It prevents users from seeing incorrect browser prompts or failed call actions when clicking telephone links created or handled by Odoo.
Original PR description
*: http_routing Since [1], the tel:// format was preferred over tel: due to reasons stated in [2]. However, the change in [2] was a workaround for a bug in the Python library used to parse URLs.…
*: http_routing Since [1], the tel:// format was preferred over tel: due to reasons stated in [2]. However, the change in [2] was a workaround for a bug in the Python library used to parse URLs. According to the relevant RFC, the tel: protocol should not include double slashes. When clicking on a link like `tel://+112351221233` in a browser, a popup may appear attempting to handle the communication using `http://tel//+112351221233` as the browser does not recognize the tel protocol when double slashes are included.   This commit removes the unnecessary double slashes to comply with RFC recommendations and just add a trailing white space to be sure that the url_parse method from werkzeug works properly. [1]: https://github.com/odoo/odoo/commit/6d4a3b3ab5c0f3361d1d681d05b974e295dcbabe [2]: https://github.com/odoo/odoo/commit/56ce29e71f75a657d4b518d86c1d7084891e898e task-4331070
Sales orders automatically created from inter-company purchase orders now use the sales team configured for the customer instead of always using the company default. This helps keep reporting, ownership, and follow-up responsibilities aligned with customer settings.
Original PR description
Sales order created from purchase orders thanks to the inter-company module were assigned the default team of the company, regardless of the customer configuration. This commit makes sure the team is correctly computed in the dedicated compute, ensuring the expected team is assigned to the Sales Order. Backport of b6b5e7ea2bb863f8ca98863c664ec3d72fcda007 opw-4166598
Miscellaneous changes
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
Original PR description
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
Currently, a traceback is occurring when the user tries to create a new put-away record and remove the `location_in_id`. To reproduce this issue: 1) Install Inventory 2) Enable multi-step routes from inventory settings 3) Create a new putaway rules record from inventory configuration 4) Remove the `when product arrives in` value Error:- ``` TypeError: startswith first arg must be str or a tuple of str, not bool ``` When the user removes the `location_in_id`, an onchange meth
Original PR description
Currently, a traceback is occurring when the user tries to create a new put-away record and remove the `location_in_id`. To reproduce this issue: 1) Install Inventory 2) Enable multi-step routes from…
Currently, a traceback is occurring when the user tries to create a new put-away record and remove the `location_in_id`. To reproduce this issue: 1) Install Inventory 2) Enable multi-step routes from inventory settings 3) Create a new putaway rules record from inventory configuration 4) Remove the `when product arrives in` value Error:- ``` TypeError: startswith first arg must be str or a tuple of str, not bool ``` When the user removes the `location_in_id`, an onchange method `_onchange_location_in` triggers. https://github.com/odoo/odoo/blob/239d18c8689d38e11783716b7e14a5204daed98a/addons/stock/models/product_strategy.py#L80-L83 We get the `loc_in` value as an empty recordset, because the user removed the `location_in_id` value. So it will lead to the above traceback from the below line https://github.com/odoo/odoo/blob/239d18c8689d38e11783716b7e14a5204daed98a/addons/stock/models/stock_location.py#L453-L455 sentry-6210564390 Forward-Port-Of: odoo/odoo#195555
The computation for the cars bik has changed in belgium for 2025. This adds rule parameters and changes the computation to reflect those changes. Task: 4409219 Forward-Port-Of: odoo/enterprise#77557
Original PR description
The computation for the cars bik has changed in belgium for 2025. This adds rule parameters and changes the computation to reflect those changes. Task: 4409219 Forward-Port-Of: odoo/enterprise#77557
- Re-exports the pots - adds `delivery_usps_rest` and `l10n_ch_payroll_elm_transmission` to be translatable - re-adds help descriptions of the codes into override in `l10n_ch_payroll_elm_transmission` field so they aren't lost
Original PR description
- Re-exports the pots - adds `delivery_usps_rest` and `l10n_ch_payroll_elm_transmission` to be translatable - re-adds help descriptions of the codes into override in `l10n_ch_payroll_elm_transmission` field so they aren't lost
Here [1] compute method does not handle multiple recordsets, The goal here is to handle more than one record at a time. This issue has been resolved in saas-18.1 by this commit [2]. [1] - https://github.com/odoo/enterprise/blob/a07631c9c58ac52866bbeb31fcf2653267190618/planning/models/planning.py#L446 [2] - https://github.com/odoo/enterprise/pull/74265/commits/8771ac92f5e0a08a052ea5ff1c423af6a3de063a Forward-Port-Of: odoo/enterprise#77970
Original PR description
Here [1] compute method does not handle multiple recordsets, The goal here is to handle more than one record at a time. This issue has been resolved in saas-18.1 by this commit [2]. [1] - https://github.com/odoo/enterprise/blob/a07631c9c58ac52866bbeb31fcf2653267190618/planning/models/planning.py#L446 [2] - https://github.com/odoo/enterprise/pull/74265/commits/8771ac92f5e0a08a052ea5ff1c423af6a3de063a Forward-Port-Of: odoo/enterprise#77970
When the user claims the document and there is no valid token Odoo tries to re-generate the token, and instead of recalling to try to claim the document the code is wrongly calling the method to accept the document This logic was added in this https://github.com/odoo/enterprise/commit/3e906a93b91b5f66a4da850acc2b5ff2f43dd267 but for reason when the methods for accept/claim were merged into one method (_l10n_cl_action_response) -- Adhoc Ticket 86396 Forward-Port-Of: odoo/enterprise#782
Original PR description
When the user claims the document and there is no valid token Odoo tries to re-generate the token, and instead of recalling to try to claim the document the code is wrongly calling the method to accept the document This logic was added in this https://github.com/odoo/enterprise/commit/3e906a93b91b5f66a4da850acc2b5ff2f43dd267 but for reason when the methods for accept/claim were merged into one method (_l10n_cl_action_response) -- Adhoc Ticket 86396 Forward-Port-Of: odoo/enterprise#78248