Tuesday, February 11, 2025
6 changes · saas-18.1
Resolved issues and error corrections
This fix prevents an error popup from appearing when staff edit a restaurant floor plan and type while adding a new floor or table. It helps keep restaurant point-of-sale setup smooth and avoids interrupting users during layout changes.
Original PR description
Check commit message for description.
Fixed an issue that could make the Discuss app crash while a call was ongoing and the sidebar showed participants. This improves reliability for users joining or viewing calls, especially when some participant details are not fully available.
Original PR description
When people were in a discuss call, the following crash may happen when discuss app is open: ``` Cannot read properties of undefined (reading 'persona') ``` This comes from template reading `channel_member.persona`, which can be undefined. Indeed, some flow may return channel member data without persona data, thus the persona is unknown (= undefined) in JS. This commit fixes the issue by taking into account persona of member that could be missing in the discuss sidebar call participant component. Task-4533395
Fixes an error that occurred when staff canceled the final remaining restaurant order. The system now safely returns users to the floor plan, helping avoid interruptions during restaurant service.
Original PR description
We check that currentOrder exist before accessing its attribute inside the function `showUnbookButton`. This was causing a traceback when canceling the last order in restaurant. After this fix, deleting the last order redirect correctly to the floorplan. Steps to reproduce : - Open "Restaurant" - Go to "Orders" - Delete all orders - For the last one (Direct sale), there is no "Delete" button in the ticket screen if the order is empty, so open it and then delete it with the action button "Cancel order" task-id: 4507062 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
Adding a work order to a manufacturing order without a selected product no longer triggers an error. The change prevents unnecessary calculations when product details are absent, improving stability during manufacturing order setup.
Original PR description
Currently, an error occurs when adding a new work order line in a manufacturing order without specifying a product. Steps to produce: - Install the `mrp` module. - Enable `Unit of measure` and `Work…
Currently, an error occurs when adding a new work order line in a manufacturing order without specifying a product. Steps to produce: - Install the `mrp` module. - Enable `Unit of measure` and `Work Orders` from the settings. - Create a new manufacturing order. - Do not specify a product in the record and attempt to add a work order. - Observe the error. Error: `AssertionError: precision_rounding must be positive, got 0.0` An error occurs when attempting to access `product_uom_id.rounding` - [1]. However, if no product is defined, the `product_uom_id` remains an empty recordset, which generates an error. [1] - https://github.com/odoo/odoo/blob/9922e570acdf695a0101a7a0c28d57a2708ea050/addons/mrp/models/mrp_workorder.py#L159 This commit resolves the issue by ensuring the product is specified, if no product is defined, the method skips the further computation to avoid errors. sentry-6236848517 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix restores access to the General Information section for bookkeepers viewing bank account-related records. It corrects a display issue that was hiding important details, helping finance users review account information without extra assistance.
Original PR description
The Book keeper was not able to see the General info of bank accounts and so on - The problem was that there was an xpath that overwrite the groups Task-4567218
This fixes a WinBooks import issue caused by a removed partner title field. Imports now correctly handle related contact records, reducing failures when bringing accounting data into Odoo.
Original PR description
…artner` children The `title` field was removed from `res.partner` in [this commit](https://github.com/odoo/odoo/commit/0b8bd891fad1c84607fe147a32d705917341fed7). A [previous fix](https://github.com/odoo/enterprise/commit/81338f4b417399d0636d5dfde47b46dec3a74d97) addressed the issue for the main partner record, but the `title` field was still being referenced for its `child_ids`. This commit ensures that child partners are also handled correctly. no-task