Thursday, October 30, 2025
6 changes · 17.0
Enhancements to existing features
This update adds identifiers to two stock transfer status fields so they can be customized separately. It helps teams and implementers adjust stock workflows more precisely without changing the visible business process.
Original PR description
IDs were incorporated into the two state fields to facilitate the process of inheriting these distinct states individually. 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
This update improves how an error is handled in the stock forecast report, making debugging more precise when an unexpected value is encountered. It helps support and development teams identify the cause faster, with minimal direct impact on day-to-day users.
Original PR description
Description of the issue/feature this PR addresses: Address the Exception precisely for debugging(Optional) Current behavior before PR: exception caused by calling field from Bool Desired behavior after PR is merged: Adresse issue when debugging --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
The website header now only creates the language selector area when more than one language is available. This prevents an empty menu spot from adding unwanted borders or spacing, keeping the header cleaner for single-language sites.
Original PR description
This PR calls the language selector placeholder only when multiple languages exist, avoiding an empty header list item that creates an unnecessary border or empty space. task-5150808 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes how IoT display devices start the Chromium browser by using the executable name expected in the latest device image. It helps ensure customer-facing displays continue to launch correctly after updating to image version 2025.11.02.
Original PR description
To ensure compatibility with the last image version 2025.11.02, we need to update `chromium-browser` executable name to `chromium`
Website navigation now marks a menu item as active only when its page URL exactly matches the page being viewed. This prevents similar page names, such as iOS and iPadOS pages, from both appearing selected and reduces visitor confusion.
Original PR description
__Current behavior before commit:__ A menu is shown as active if the unslug version of its URL matches the current accessed URL. The issue is that the unslug version of a menu linked to a page has no real meaning. Such menu should only be shown as active if the request URL path matches exactly. __Description of the fix:__ Added a check to ensure that when a menu is linked to a page, it isn't shown as active if its path doesn't exactly match the request path. __Steps to reproduce:__ 1. On the website, go to Site > Pages 2. Create a new page with title "iOS 26" and another page with title "iPadOS 26" 3. Go to /ios-26 4. Both menus "iOS 26" and "iPadOS 26" are highlighted task-5094899
This fix ensures alert blocks added to checkout extra-step description fields stay inside the editable area. Website editors can now add and modify alert content in those descriptions without the content becoming locked or unusable.
Original PR description
Problem: When adding an alert inside a field description in the Extra Step page of the checkout process, the inner content of the alert cannot be modified. Cause: In…
Problem:
When adding an alert inside a field description in the Extra Step page of the checkout process, the inner content of the alert cannot be modified.
Cause:
In
https://github.com/odoo/odoo/blob/1e96a3d127e8f521d3027f7110026ae84e11ed5e/addons/website/static/src/components/wysiwyg_adapter/wysiwyg_adapter.js#L784-L789 the logic determines the block using:
`this.closestElement(range.endContainer, 'p, div, ol, ul, cl, h1, h2, h3, h4, h5, h6');` Since the field description template is:
```html
<div class="s_website_form_field_description small form-text text-muted"
contenteditable="true">
text
</div>
```
and the selection occurs within the text (direct child of the editable `div`), the computed `block` becomes the editable area itself. As a result, the cloned alert is inserted *after* the editable area: `block.after($clonedBody[0]);`, making it non-editable.
Solution:
Use the editor’s built-in `insert` command instead of manually inserting clones. This ensures the alert is correctly inserted within the editable region.
Steps to reproduce:
1. Enable "Extra Step During Checkout" in Settings.
2. Open Website → add a product to the cart → proceed to checkout.
3. In the "Extra info" step, open the editor.
4. Select the "Give us your feedback" field.
5. Enable "Field" → "Description".
6. Run the "/alert" command in the description. → The alert content cannot be edited.
opw-5184309
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr