Monday, March 17, 2025
5 changes · 17.0
Resolved issues and error corrections
This fix prevents an internal error when the same grouping option is used more than once in data summaries. It helps keep grouped reports and calculations reliable instead of failing unexpectedly in this edge case.
Original PR description
Since https://github.com/odoo/odoo/pull/103510 , _read_group raises a StopIteration error if there are duplicate groupby specifications. This is because `groupby_terms` has become a `dict` which doesn't allow duplication but we are still looping on the `groupby` list to retrieve columns, leading to raise a StopIteration error when we try to retrieve the last column. Fix this by creating `groupby_terms` with `groupby` instead of values from the dict.
The Discuss call interface now shows connection warning icons only when appropriate. This removes a misleading warning from the user's own call card in small calls and restores the intended warning behavior when using server-based calls.
Original PR description
Before this commit, when making or joining a discuss call with up to 2 participants, it was always showing a warning icon in the top-right corner of the self card. This happened because the code to…
Before this commit, when making or joining a discuss call with up to 2 participants, it was always showing a warning icon in the top-right corner of the self card. This happened because the code to show connection issue on card filters on self session: warning icon on other sessions in P2P, and on self card when using SFU server. This was using `rtc.selfSession` to compare sessions, but this is correct only starting from 17.4. In 17.0, the `selfSession` is stored in `rtc.state.selfSession`. Because of this typo, the warning icon is always displayed on self card in P2P. This commit fixes the issue by using `rtc.state.selfSession`. Note that SFU branching for conditionally showing the icon was also wrong. This made it never show the triangle warning icon. This is also fixed by this commit. Before <img width="2261" alt="Screenshot 2025-03-17 at 11 36 07" src="https://github.com/user-attachments/assets/b11272b2-df95-4470-b9e5-ec6bd643b153" /> After <img width="2265" alt="Screenshot 2025-03-17 at 11 36 32" src="https://github.com/user-attachments/assets/f00a4978-d8cd-4201-a629-02618e71f381" />
Manufacturing orders now stay linked to their component stock movements even when components were not available for reservation. This makes the Moves History report more reliable when users filter by manufacturing order.
Original PR description
When producing a MO with components and the components don't have any available quantity, there are no direct link between the MO and the stock move lines of its move_raw_ids. This causes issues when filtering on MO in the Moves History report. This is because the link is only done at the reservation of the SMLs, which can't happen without available qty. This fix ensures that the MO is added at the SML creation. opw-4545828 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The online shop cart now correctly records when the final item has been removed. This prevents customers from seeing an unnecessary confirmation message when reordering from their portal after their cart is empty.
Original PR description
Steps: - Install Ecommerce - Add some products to the cart - Remove them using the 'remove' option - Go to my/orders - select any order, then click on Order again - Click on the Add To Cart button - You'll see one confirmation dialog Issue: - By clicking on the add to cart button, that confirmation dialog should not be there as the cart is empty Cause: - Cart quantity does not update when the last product is removed Fix: - While removing the last product, set cart quantity in sessionstorage to ensure that the last removal is recorded affected version-17.0 opw-4566505 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The mail call interface now stops showing who is speaking when a user has deafened themselves. This prevents distracting or irrelevant call activity indicators for users who have chosen not to hear the conversation.
Original PR description
Current behavior before PR: `isTalking` status displayed who was talking even when the user had deafened themselves. Desired behavior after PR is merged: `isTalking` status no longer shows who is talking if the user has deafened themselves. Task-id:[4609755](https://www.odoo.com/odoo/project.task/4609755) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr