Tuesday, July 22, 2025
6 changes · saas-18.2
Resolved issues and error corrections
New messages received while the Discuss app is open no longer create hidden chat bubbles that appear later. Users still receive notifications, and live chat conversations continue to open bubbles as expected.
Original PR description
**Current behavior before PR:** Receiving a new message while the Discuss app is open creates a chat bubble in the background. These bubbles become visible after leaving the Discuss app. **Desired behavior after PR is merged:** Chat bubbles are no longer created while the Discuss app is open, except for livechat messages. Messages still trigger notifications, but no background bubbles are inserted. task-[4752392](https://www.odoo.com/odoo/project/1519/tasks/4752392) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#219796 Forward-Port-Of: odoo/odoo#215125
This fixes an issue where pressing Tab in website edit mode could trigger an error if no text cursor was active. Website editing navigation is now more stable and avoids interrupting users with a traceback.
Original PR description
This PR fixes traceback issue: Steps to Reproduce for 1st traceback: 1. Go to Website in edit mode. 2. Click on the menu in the header such a way that the cursor is not placed inside. 3. Press the tab key. 4. You will receive the traceback. Issue: When the selection is null, the anchorNode also becomes null, resulting in closestUnbreakable being null. Therefore, we should avoid accessing nodeName on a null element to prevent errors. Fix: Safely access elements using optional chaining to prevent errors when elements are not found. task-4577864 Forward-Port-Of: odoo/odoo#200548
The accounting test setup now initializes the required data even when demo data is not loaded. This prevents sale flow test failures in leaner test databases, improving reliability for validation and releases.
Original PR description
Current behavior before PR: Tests for the sale flow fail due to missing variables if there is no demo data. Desired behavior after PR is merged: Tests no longer fail, as data is initialised properly. runbot-227766 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#217660
E-invoice exports now include product barcode information in the same standard field already used when importing invoices. This improves consistency between imported and exported electronic documents and helps trading partners identify products more reliably.
Original PR description
[FIX] account_edi_ubl_cii: export product barcode too Currently we use the `Item/StandardItemIdentification` as the barcode when importing a product. But we do not export the same information. In 18.0+ the `Item/StandardItemIdentification` was added to the UBL XML (for exporting) in commit 72e312815f372de88388c47c612bb5f44b4d8b4e. But there it is only used in `l10n_co_dian`. After this commit we export and fill the tag "by default". task-4941855 Forward-Port-Of: odoo/odoo#219391 Forward-Port-Of: odoo/odoo#218779
This fix makes automated website tours handle page changes more reliably when moving to a new URL. It reduces inconsistent tour failures caused by page unload events, helping teams maintain more stable testing and validation flows.
Original PR description
In this commit, we add expectUloadPage to goToUrl util. This util redirect to another page an involves a unload event so we need to add this key to this util to avoid undeterministic behaviors in tours that use it. 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#219672
This fix simplifies an automated portal signing test by removing a fragile step that depended on another app. It helps keep validation checks more reliable without changing the signing experience for users.
Original PR description
We remove the last step, which depends on the mail module and is too complex. The reason for this step was to avoid a failed to fetch received after termination. This problem must be solved in another way. runbot-error-id~163605 Forward-Port-Of: odoo/enterprise#84480