Monday, September 8, 2025
9 changes · saas-18.2
Resolved issues and error corrections
The checkout flow now avoids sending the same address update more than once when billing and shipping use the same address. This reduces unnecessary processing and helps make checkout submission more reliable for customers.
Original PR description
## Issue When the shipping and billing addresses are the same during checkout, the `/shop/update_address` route is called multiple times unnecessarily. ## Current Behavior - `updateAddress` is always invoked before checking whether the address is a delivery address or if `this.billingContainer.dataset.deliveryAddressDisabled` is set. - If the condition is met, the method is called again, resulting in duplicate requests. ## Steps to Reproduce 1. Add a product to the cart. 2. Start the checkout process. 3. In the address step, select the same address for both shipping and billing. 4. Submit the form. 5. Multiple calls to `/shop/update_address` are triggered. ## Expected Behavior - `updateAddress` should only be called once after verifying the condition. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Analytic line amounts now use the company's currency rounding instead of a foreign currency's rounding. This prevents amounts from being shown too coarsely, helping accounting reports and analytic details display the expected precision.
Original PR description
Steps to reproduce: - set the rounding of a foreign currency to 1.0 - have you company currency's rounding to 0.01 - create a move with a line with an analytic distribution - post it - go to analytic line Issue: The amount will be displayed with a rounding of 1.0 and not 0.01 opw-4997047 Forward-Port-Of: odoo/odoo#225503
This fix updates automated checks for chat and live chat so they no longer fail unpredictably when a keyboard shortcut conflicts with command suggestions. It helps keep release validation stable without changing the customer-facing messaging experience.
Original PR description
\* = crm_livechat, im_livechat Back-port of 3fc3e4fbbd846dc8f65938a0bfbddbebf2abc403 Enter after typing a command will either send the message when the suggestion list is not opened yet, or select the suggestion. This can either be fixed by waiting for the suggestion list to be opened, closing it, and then pressing enter, or by simply clicking on the send button which is what is done here as the way the message is sent is irrelevant for these tests. https://runbot.odoo.com/odoo/runbot.build.error/230977
Website submenus now use colors that adapt correctly when a sidebar header has a dark background. This prevents submenu text and backgrounds from blending together, making navigation usable for site editors and visitors.
Original PR description
Steps to reproduce: - Install the "Website" app. - Go to the homepage. - Click on "Site > Menu Editor" in the backend navbar. - Create a submenu. - Save the dialog. - Enter edit mode. - Click on the header. - Choose a dark background in the header options. - Choose the "Sidebar" template in the header options. - Open the submenu. - Bug: The submenu is not visible because the background and text have the same light color, so nothing can be seen. The bug was introduced by commit [1], which made visual improvements to the menu. This commit fixes it by making sure the colors of the problematic elements adapt to the theme colors. [1]: https://github.com/odoo/odoo/commit/dc1a15539227c4c21837a7bce3fc4d81858d60b9 opw-5043010
This fix makes the mail message state easier for automated checks to detect after a user marks a message as a to-do. It reduces recurring test failures without changing the visible user experience.
Original PR description
Backport of https://github.com/odoo/odoo/pull/216106 Before this commit, test "test_star_message" was failing frequently on runbot at step to check message was starred have click on "Mark as Todo". This happens because when click on mark as todo, the message is asynchronously starred. However, there's no visual indication other than the message action have yellow filled star icon. This requires hovering the message to see it, but we don't know when we should exactly hover the message to see it. This commit fixes the issue by adding a `data-starred` on the `o-mail-Message` root node of message template that tells whether the message is starred or not. This removes necessity to hover to check whether message is starred. Fixes runbot-227568 Forward-Port-Of: odoo/odoo#225867
This update makes automated checks for the Discuss command palette more stable by ensuring the interface is ready before actions are tested. It reduces false test failures and improves confidence in related messaging and search behavior without changing day-to-day user workflows.
Original PR description
Before this commit, clicking on some elements of the command palette would not trigger the associated event, this was probably caused by clicking on outdated owl fragments which cannot trigger events while being destroyed. This commit fixes this issue by making sure that the interface is in a stable configuration before clicking. The commit also fixes the mock of `discuss/search` ( for https://github.com/odoo/enterprise/pull/94075 ) and a test that was incomplete and relied on the incorrect implementation https://runbot.odoo.com/odoo/runbot.build.error/112148
This fix addresses a timing issue that could occur when users sent messages with Command+Enter in enterprise chat-related features. It helps prevent unreliable behavior in helpdesk live chat and discussion tests, improving message sending consistency.
Original PR description
\* = test_discuss_full_enterprise, website_helpdesk_livechat Back-port of 14b31a3631a97dd61ebd662fb768485e5a509c2c Enterprise counter-part. https://runbot.odoo.com/odoo/runbot.build.error/230977
This fix makes automated WhatsApp command palette tests wait until the interface is stable before interacting with it. It reduces false test failures, helping keep development and release validation more reliable without changing user-facing behavior.
Original PR description
Before this commit, clicking on some elements of the command palette would not trigger the associated event, this was probably caused by clicking on outdated owl fragments which cannot trigger events while being destroyed. This commit fixes this issue by making sure that the interface is in a stable configuration before clicking. https://runbot.odoo.com/odoo/runbot.build.error/112148
The point-of-sale Pricer feature now avoids an error when users work with product variants that have not been saved yet. Users can set the Pricer Sales Pricelist after saving the variant, preventing crashes and keeping product setup smoother.
Original PR description
An error occurs when a user attempts to set the **Pricer Sales Pricelist** on a product variant that has not yet been saved. **Steps to reproduce:** - Install the `pos_pricer` module. - Open the form…
An error occurs when a user attempts to set the **Pricer Sales Pricelist** on a product variant that has not yet been saved. **Steps to reproduce:** - Install the `pos_pricer` module. - Open the form view of **Product Variants**. - Without saving the record, try to add a **Pricer Sales Pricelist**. - Observe the error. **Error:** `KeyError: False` **Cause:** When the product variant is unsaved, `product._origin` is `False`, leading to a `KeyError` at [1], because `False` is not a valid key in the evaluation of method `_get_product_price()`. [1] - https://github.com/odoo/enterprise/blob/6f96632f23c3955b874a9019ba6a92561dec3172/pos_pricer/models/product_product.py#L139 This commit ensures the `pricer_sale_pricelist_id` field is invisible for unsaved product variant records to avoid inconsistent behavior. It allows users to only set a pricelist after the record has been saved, preventing any invalid computations or errors. Sentry - 6598605111,6696068013 Forward-Port-Of: odoo/enterprise#86506