Daily updates from Odoo
Thursday, January 1, 2026
4 changes · saas-18.4
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
A minor typo in the l10n_ec_edi_pos module prevented the correct partner (Deco Addict) from being selected when processing refunds. This fix corrects the typo, ensuring refunds are handled accurately for Ecuadorian POS transactions. This resolves a potential issue with reporting and reconciliation.
Original PR description
Step to reproduce: - install l10n_ec_edi_pos - start pos and settle order with specific partner(ex. Deco Addict) - process the refund for this order Observation: - on product screen, "Consumidor Final" is selected instead of Deco addict. Cause and Fix: - Fixed a typo: it used `final_consumer_id` instead of `_final_consumer_id` opw-5412346 Forward-Port-Of: odoo/enterprise#102998 Forward-Port-Of: odoo/enterprise#102202
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
This update resolves an error that prevented users from opening the employee form within the Point of Sale (POS) frontend. The fix disables the employee form link on the frontend only, allowing it to function correctly in the backend where all necessary data is available. This ensures a smooth user experience for POS operations.
Original PR description
Opening employee form in the frontend was throwing an error, since not all thre required assets were available on the PoS frontend. So in this commit 57aba149b6e6927f9055124e58bed03f842329d5, we disabled openening the employee form by making the employee_id field unclikcable, both in forntend and backend!! It was enough however to only macking it unclikcable on the frontend, since it was working fine on the backend where all the required assets were loaded anyway. This commit restores the functionality on the backend, but overriding the `Many2OneField` used by the `employee_id`, and making it unclickable only on the frontned. opw-5252486 Forward-Port-Of: odoo/odoo#241100