Sunday, September 20, 2026
5 changes · master
Resolved issues and error corrections
Color choices without a manually selected color now display properly in the Add to Cart popup, matching the product page. This avoids confusing gray swatches and helps shoppers recognize the intended product options before purchasing.
Original PR description
Issue: Color attribute values without an explicit html_color show correctly on the product page but render as a plain gray circle in the "Add to cart" popup / product configurator, even though selecting them still works. Steps to reproduce: 1. Create a Color attribute value without picking a color (leave the Color field unset) and add it to a published product. 2. Open the product page: the swatch shows fine. 3. Click Add to Cart to open the popup: the swatch is a plain gray circle instead. Cause: product_template_attribute_line.xml (sale.ptav_color) used `ptav.html_color` directly with no fallback, producing the invalid CSS "background-color:false" when html_color is unset. Fix: Apply the same `html_color or name` fallback in the configurator's color-swatch template. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#288582
The Documents action menu now shows the expected visual highlight when users hover over the Action option in the kanban view. This makes the interface feel more responsive and helps users clearly see which menu item they are about to select.
Original PR description
Bug === 1. make sure to have actions pinned on a folder 2. right-click a document in the kanban view 3. hover the "Action" item => there's no hover effect Task-6563359 Forward-Port-Of: odoo/enterprise#132157
Users can once again click "Add a stream" in the Social feed view without encountering an error. This restores a normal workflow for managing social media monitoring streams and avoids disruption for teams using the Social app.
Original PR description
Since 05a073df3bb5fead98702aa59a5c83c5076c7f03 a traceback is raised when clicking on "Add a stream" in the social feed view. Task-6584714 Forward-Port-Of: odoo/enterprise#132152
The messaging menu now correctly loads the latest OdooBot welcome message for new users instead of showing an empty conversation placeholder. This ensures users see the right chat preview and can clear the unread notification as expected.
Original PR description
Before this commit, the OdooBot conversation showed "This is the start of your conversation" instead of the last message of OdooBot, and could not be marked as read. Steps to reproduce: - log in as a…
Before this commit, the OdooBot conversation showed "This is the start of your conversation" instead of the last message of OdooBot, and could not be marked as read. Steps to reproduce: - log in as a new internal user, so that the onboarding creates the OdooBot chat and posts its welcome message - open the messaging menu, "Chats" tab - the OdooBot conversation shows no message preview, and marking it as read leaves its unread counter at 1 This happened because the messaging menu excluded from its own fetch every channel already in the store, no matter how it got there. `init_messaging` adds the OdooBot chat without its last message: it only needs the channel itself, to auto-open the chat during onboarding. So the message was never loaded, while both the preview and `markAsRead` needed it client side. This commit fixes the issue by no longer relying on the mere presence of the channel in the store: it is excluded only if its last message has been fetched too, either because the server sent it along the channel (new `lastMessageFetched` flag, set by the routes requesting the last messages of the channels they add to the store), or because the thread has been loaded, in which case its messages necessarily contain the last one. (See the Odoobot notification's message) <img width="396" height="630" alt="before-master" src="https://github.com/user-attachments/assets/c67ce8cf-a363-4fb6-94fa-2ada9ba08e4b" /> <img width="396" height="630" alt="after-fix" src="https://github.com/user-attachments/assets/bb74ee5a-3f5f-4b8a-bfd1-5662d7a52dca" /> Forward-Port-Of: odoo/odoo#287749
Adds test coverage for a case where Avalara tax details are recalculated after an exemption certificate is uploaded. This helps ensure product line tax data stays aligned with the generated tax lines, reducing the risk of incorrect tax reporting or invoice totals.
Original PR description
We removed the explicit tax clearing [1]. It ends up triggering a situation where extra_tax_data on the product lines diverges from the tax lines. This happens when the tax integration writes only extra_tax_data without modifying anything else on the lines (if e.g. you first calculate tax, upload the exemption certificate to Avalara, and then recalculate tax). This tests that exact scenario. opw-6547387 [1] https://github.com/odoo/enterprise/pull/107863 Forward-Port-Of: odoo/enterprise#132083 Forward-Port-Of: odoo/enterprise#131815