Monday, July 8, 2024
8 changes
3 changes
Resolved issues and error corrections
This update brings the spreadsheet component to a newer version with several fixes for common spreadsheet actions. It improves reliability when deleting rows, pasting content, using number formats, charting cumulative data, and working with broad cell references, reducing user-facing errors in spreadsheet workflows.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/acfb3e71e [REL] 17.2.15 Task: 0 https://github.com/odoo/o-spreadsheet/commit/6ea19c264 [FIX] border: bottom sheet…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/acfb3e71e [REL] 17.2.15 Task: 0 https://github.com/odoo/o-spreadsheet/commit/6ea19c264 [FIX] border: bottom sheet borders removed on DELETE_ROWS Task: 3911695 https://github.com/odoo/o-spreadsheet/commit/6497e8c6a [FIX] locale: handle undefined thousands separator Task: 0 https://github.com/odoo/o-spreadsheet/commit/c2d6eab35 [FIX] chart: cumulative not working for linear charts Task: 4028957 https://github.com/odoo/o-spreadsheet/commit/f00e760ee [FIX] grid: prevent paste default Task: 3949903 https://github.com/odoo/o-spreadsheet/commit/a59ed517f [FIX] parser: `parse` should handle unbounded references Task: 4010920 Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com> Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com> Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com> Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com> Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com> Co-authored-by: Mehdi Rachico (mera) <mera@odoo.com> Co-authored-by: Rémi Rahir (rar) <rar@odoo.com> Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com> Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>
This fix stops the web interface from registering the same template extension more than once. It reduces the risk of unexpected crashes when duplicate frontend assets are loaded, improving stability for users.
Original PR description
Before that commit, it was possible to register several times the same template extension. This can lead to crash in some occasions. For example consider the template
```xml
<t t-name="A">
<div attr="a" />
</t>
```
and its extension
```xml
<t t-name="B" t-inherit="A" t-inherit-mode="extension">
<xpath expr=".//div[@attr='a']" position="attributes">
<attribute name="attr">b</attribute>
</xpath>
</t>
```
In that case, when building the template A with B registered twice, the first application of B to A will succeed while the second application will cause a crash (no target found for the xpath).
Here we prevent multiple registering of the same template extensions. Note that this is similar to what happens when the same js module is received several times: odoo.define has no effect after the first registering.The message composer now displays recipient names and joining words with proper spacing in the chatter. This makes the recipient list easier to read and avoids a small visual glitch when sending messages.
Original PR description
Before this commit the recipients list displayed when sending a message on the chatter missed spacing between the recipients and conjunctions. This happens because the container has display flex which removes whitespace from child elements. This commit fixes the issue by wrapping the list in a div tag so to preserve the whitespace. task-4032550 Before:  After: 
1 change
Resolved issues and error corrections
This fixes an error that could occur when an employee was assigned to a preparation display order in Point of Sale. It helps keep kitchen preparation workflows stable and avoids interruptions during order handling.
Original PR description
Fix traceback when assigning employee_id to pdis order. taskId: 4037944
4 changes
Resolved issues and error corrections
This fix corrects how shift times are displayed when employees view open scheduling opportunities via email links. Previously, shift times were incorrectly shown in UTC regardless of the employee's location. Now they display in the employee's local timezone, making scheduling information clearer and more accurate for global teams.
Original PR description
Versions -------- - 16.0+ Steps ----- 1. Create an open slot in a planning; 2. publish & send an email to an employee who could fill it; 3. open the planning link sent via email; 4. open the same URL while logged out. Issue ----- The datetimes of the open slot are displayed in UTC. Cause ----- Commit cf256e94d333 modified the planning template to use the `datetime` widget to format the dates instead of the `format_datetime` function provided by the `ShiftController`. Doing so, it lost access to the `employee_tz` value, derived from the email recipient, and hence defaulted to UTC. Solution -------- Format the dates using `format_datetime`. opw-3967787 Forward-Port-Of: odoo/enterprise#66015
This update corrects how expense accounts are classified in Danish financial reports. The "Purchase of goods" account was reclassified from a general expense to a direct cost category, which ensures the test data accurately reflects the proper account ordering in reports. This fix ensures Danish compliance reporting works correctly.
Original PR description
[FIX] l10n_dk_reports: fix account type of DK report tests By fixing the type of the account "Purchase of goods" from expense to expense_direct_cost the test now takes the new first expense account which is now "Freight costs" and not "Purchase of goods" anymore task-id#3983710 odoo-pr#[168838](https://github.com/odoo/odoo/pull/168838)
This fix resolves an issue where quantities displayed in the barcode scanning system showed excessive decimal places (like 10.1000000001 instead of 10.1) when packing products. The system now properly rounds quantities to the appropriate decimal precision, ensuring cleaner and more accurate quantity displays for warehouse staff.
Original PR description
Current behavior: --- When putting product in packs, the quantity done amount can be like 10.1000000001 Expected behaviour: --- Should be rounded to 10.1 Steps to reproduce: --- 1. Install Purchase 2. Go to Settings, Inventory 3. Activate Packages 4. Go to Products 5. Create a new product 6. Set inventory > Tracking: By Lots 7. Go to Purchase, new Requests for Quotation 8. Add the new lot product, quantity 13.5 9. Click on Confirm order 10. Go to Barcode, operations, receipts 11. Select the last created receipt 12. Edit the line, input 5.66, save 13. Click on Put in pack 14. Select the empty line in the pack 15. Input 4.44, save 16. The first quantity is 10.1000000001 opw-3821629 Forward-Port-Of: odoo/enterprise#59401
This fix resolves an issue where optional products were not visible in the customer portal preview for subscription orders that have a start date set but are still in draft status. The system now correctly displays optional products regardless of whether the invoice date has been calculated yet, improving the customer experience when reviewing their subscription details before confirmation.
Original PR description
### Steps to reproduce: - Install Sale Subscription module - Create a recurrent order and add Optional products and Start date under Other info tab - Click on Preview ### Current behavior before PR: You won't see the optional products in the portal view if for a recurrent order that has start date and in draft. This is happening because in sale_subscription we are checking if the start_date of the order is equal to the next_invoice_date https://github.com/odoo/enterprise/blob/17.0/sale_subscription/models/sale_order.py#L1957:1959 and if the order is in draft it won't have a next_invoice date until it is either confirmed or sent. ### Desired behavior after PR is merged: We are now checking if the next_inovice_date is not set we show the optional products. opw-3980405