Daily updates from Odoo
Thursday, January 1, 2026
6 changes
1 change
Resolved issues and error corrections
This update automatically marks UrbanPiper orders as paid in Odoo when they are marked as 'dispatched'. This prevents orders from being accidentally cancelled due to missed payment marking, improving the POS process. It also ensures UrbanPiper orders are tracked within Odoo's internal systems.
Original PR description
*= urban_piper, black_box_be In this commit: =============== - When UrbanPiper updates an order to `dispatched`, we now automatically mark the order as paid in Odoo. - This prevents the order from being cancelled during the POS session closing if the cashier forgot to mark it as ready. - Also, we are adding this urban piper order to the blackbox, if it was not recorded in it. Task: 5261892 X-original-commit: 808cf7b3f8c185053dac5cbf75307efa67fd6e90 Forward-Port Of:odoo/enterprise#99513 Forward-Port-Of: odoo/enterprise#103102 Forward-Port-Of: odoo/enterprise#102346
2 changes
Resolved issues and error corrections
This update fixes an issue where combo line prices were incorrectly set to 'automatic' after order creation, leading to pricing inconsistencies. The change ensures combo line price types remain as originally set, allowing for accurate price updates and preventing conflicts with order processing. This improves the reliability of combo line pricing in point-of-sale transactions.
Original PR description
After commit https://github.com/odoo/odoo/commit/69057e41fb4cd800d23401ead8ae11bf7cba7c64, the price type of combo lines was changed to 'automatic' when creating the combo line. This caused the set pricelist logic to update the price of combo lines with automatic price type, which conflicts with the intended behavior. This commit ensures that the price type of combo lines is preserved as original in cases where we want to update the price, and only set to automatic in cases like loading a sale order or refunding an order. opw-5240429 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#241481 Forward-Port-Of: odoo/odoo#234575
This update fixes a technical issue where joining a meeting from multiple browser tabs could cause a crash. The change ensures stability when users participate in calls across different tabs, improving the overall meeting experience. This resolves a bug related to how the call's RTC session is handled.
Original PR description
**Steps to reproduce:** - Start a meeting with user A - Share the invitation link with user B - Login with user B and join the call - Open another browser tab/window with the same user B - Join the same call in that tab using the invitation link - The call ends for that user as the RTC session is terminated - **_TAB1_**: join the call again - **_TAB2_**: error **Current behavior before PR:** When the same user joined the same call from another tab or during RTC renegotiation, selfSession could temporarily be undefined. **Desired behavior after PR is merged:** This PR ensures that no crash happens when dealing with the RTC Session in a `multi-tab` scenario. task-[5263097](https://www.odoo.com/odoo/project/1519/tasks/5263097) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#241578 Forward-Port-Of: odoo/odoo#240881
1 change
Resolved issues and error corrections
This update automatically marks UrbanPiper orders as paid in Odoo when they are marked as 'dispatched'. This prevents order cancellations due to missed payment marking during POS closing, improving efficiency and reducing potential errors. It also ensures UrbanPiper orders are tracked within Odoo's internal systems.
Original PR description
*= urban_piper, black_box_be In this commit: =============== - When UrbanPiper updates an order to `dispatched`, we now automatically mark the order as paid in Odoo. - This prevents the order from being cancelled during the POS session closing if the cashier forgot to mark it as ready. - Also, we are adding this urban piper order to the blackbox, if it was not recorded in it. Task: 5261892 X-original-commit: 808cf7b3f8c185053dac5cbf75307efa67fd6e90 Forward-Port Of:odoo/enterprise#99513 Forward-Port-Of: odoo/enterprise#103102 Forward-Port-Of: odoo/enterprise#102346
1 change
Resolved issues and error corrections
This update automatically marks UrbanPiper orders as paid when they are marked as 'dispatched'. This prevents order cancellations due to missed payment marking during POS closing, improving efficiency and reducing potential errors. The update also ensures UrbanPiper orders are tracked within Odoo's internal systems.
Original PR description
*= urban_piper, black_box_be In this commit: =============== - When UrbanPiper updates an order to `dispatched`, we now automatically mark the order as paid in Odoo. - This prevents the order from being cancelled during the POS session closing if the cashier forgot to mark it as ready. - Also, we are adding this urban piper order to the blackbox, if it was not recorded in it. Task: 5261892 X-original-commit: 808cf7b3f8c185053dac5cbf75307efa67fd6e90 Forward-Port Of:odoo/enterprise#99513 Forward-Port-Of: odoo/enterprise#102346
1 change
Resolved issues and error corrections
This update resolves an issue where removing an icon from a paragraph would leave it unusable. The fix ensures that paragraphs remain editable and accessible after icon removal, improving the user experience. It also addresses a bug where pressing 'Enter' before an icon wouldn't insert a new paragraph.
Original PR description
**Issue 1:** Steps to reproduce: - Insert a icon in an empty paragraph. - Remove the inserted icon. - The paragraph becomes unreachable. Cause: - When a paragraph contains only an icon, removing that…
**Issue 1:** Steps to reproduce: - Insert a icon in an empty paragraph. - Remove the inserted icon. - The paragraph becomes unreachable. Cause: - When a paragraph contains only an icon, removing that icon during the delete process does not trigger `fillEmpty`. As a result, the paragraph ends up with no content, leaving it empty and unreachable. Solution: - During the delete process, after the icon is removed, call the `fillEmpty` method. This ensures that if the block becomes empty, a `<br>` is inserted inside the paragraph, keeping it accessible. **Issue 2:** Steps to reproduce - Insert an icon in an empty paragraph. - Place the cursor before the icon. - Press Enter. - Nothing happens. Cause - When the cursor is placed before a `contenteditable=false` element, `getDeepRange` sets the selection deep inside the non-editable element as a result, when Enter is pressed, the action is ignored because the selection is not in an editable context. Solution - Instead of setting the selection inside `getDeepRange`, set the selection after calling `getDeepRange` only if the returned range is not within a `contenteditable=false` element. task-3540454 Forward-Port-Of: odoo/odoo#241052 Forward-Port-Of: odoo/odoo#237891