Saturday, August 15, 2026
9 changes · 19.0
Enhancements to existing features
Canceled POS orders in the Belgian blackbox flow no longer wait for receipt printing to finish. This helps staff complete cancellations more quickly and avoids unnecessary delays when a receipt print is slow or not needed.
Original PR description
Stop awaiting the receipt print in the POS for canceled orders task-id: 6425204 community PR: https://github.com/odoo/odoo/pull/280002
Resolved issues and error corrections
Invoices created from POS sales linked to sales orders now keep the customer reference from the original sales order. This helps businesses maintain clearer invoice records and trace orders accurately, especially when multiple POS orders are consolidated.
Original PR description
The pos_sale override of _prepare_invoice_vals left ref and invoice_origin untouched, so the SO's client_order_ref was lost on the invoice. The fix is to mirror sale.order._prepare_invoice and set both fields from the linked SO, while preserving pos_reference traceability for mixed consolidated batches. task-id: 6295629 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change makes an automated test for table selection in the HTML editor wait until the editor is ready before continuing. It helps prevent false failures in busy test environments, improving confidence in release validation without changing user-facing behavior.
Original PR description
On highly loaded runbots, waiting a single animation frame might not be sufficient for the table deselection to be available in the DOM after a key press. This commit waits for the table to be deselected before continuing the test. runbot-944722
The ecommerce product page now hides the product specifications table when none of a product's tags are marked visible online. This prevents shoppers from seeing an empty table, making product pages cleaner and less confusing.
Original PR description
The product specifications table is displayed whenever the product has tags, even if none of them are visible on the ecommerce website. The product tags template filters out non-visible tags, but the…
The product specifications table is displayed whenever the product has tags, even if none of them are visible on the ecommerce website. The product tags template filters out non-visible tags, but the surrounding table remains rendered and appears empty. Only display the tags table when at least one tag is visible on ecommerce. @Tecnativa TT63855 **Description of the issue/feature this PR addresses:** The condition used to display the product tags table considers all tags associated with the product, including those that are not visible on ecommerce. **Current behavior before PR:** When a product only has non-visible tags, the tags table is displayed without any content. <img width="669" height="350" alt="image" src="https://github.com/user-attachments/assets/4758ea76-5186-4035-a065-aa4c71ce7053" /> **Desired behavior after PR is merged:** The tags table is only displayed when the product has at least one tag visible on ecommerce. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#280514 Forward-Port-Of: odoo/odoo#278604
Sample spreadsheet dashboard figures are now non-clickable, matching their faded appearance as placeholder data. This prevents users from accidentally interacting with demo values and reduces confusion when viewing sample dashboards.
Original PR description
In the sampel dashboard the figures are half transparent to indicate that they are just sample data, but they are still interactive. This commit disable all the pointer events on them. Task: [6467022](https://www.odoo.com/web#id=6467022&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) 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 Forward-Port-Of: odoo/odoo#282179
French companies will still see guidance about installing the PDP module even when it has not yet appeared in the app list. The warning now points users to refresh the app list first, helping them complete the setup without getting stuck.
Original PR description
In commit 004b56a5c31841bc0bf4a9f17902bbff8d0f509d we added
warnings to tell French companies to install the PDP module.
When working on commit 720294ee523c6f84d0302e6b7fd634069f72dda7
we noticed the problem that the PDP module is not available
without rescanning the available modules ("Update Apps List" in
debug mode in the "Apps").
This is fixed in this commit:
In case the module is not installed we still show the warning
but link to the "Update Apps List" wizard.
task-None
Forward-Port-Of: odoo/odoo#280209The Polish bank verification module now avoids a setup failure during installation or upgrades. This helps businesses using Polish payment verification complete deployments without interruption.
Original PR description
At installation of the l10n_pl_bank_verification module or when upgrading from a lower version, the field l10n_pl_verification_id on the account.payment model gets computed and it makes the upgrade crash out. Adding a init to the model to create the column to prevent the ORM from computing the field at module installation no-task Forward-Port-Of: odoo/odoo#282504
The customer portal account details page now shows the expected breadcrumb when users edit their information. This helps users understand where they are in the portal and navigate back more easily.
Original PR description
Steps: - Install portal app. - Go to my/home page. - Click on `Edit information` button. Issue: - There is no breadcrumb in `my/account` page. Cause: - After [PR](https://github.com/odoo/odoo/pull/190312) page_name of `my/account` page `my_details` was overridden by `home` from `_prepare_portal_layout_values` method. Fix: - Set page_name `my_details` after `_prepare_portal_layout_values` method call to properly set page_name. Forward-Port-Of: odoo/odoo#279072
This fix prevents Odoo's web test tools from adding an incorrect content type to mocked responses. It makes automated tests more reliable, especially when responses use streams, reducing false failures during development.
Original PR description
Before this commit, a test answering a route with a response of its own, `new Response(stream)`, reads `content-type: application/json` back from it, a header it never set. At the debug log level, the request itself fails:
Unexpected token 'o', "[object Rea"... is not valid JSON
This happens because the mocked fetch guesses the content type from its result, and a response is neither a string, a `Blob` nor a `FormData`, so it falls back to JSON, on the very headers the response carries. The response logger then reads the body as text, "[object ReadableStream]" for a stream, and parses it as JSON.
This commit guesses the content type of a raw value only, so a response keeps the headers it was built with.
Forward-Port-Of: odoo/odoo#281968