Odoo Changelog — 2025-03-05

Wednesday, March 5, 2025

55 changes · saas-18.2

Bug Fixes(2)

Resolved issues and error corrections

[FIX] web: prevent effect duplication for useRecordObserver

PR #200006

Coresaas-18.2web

This fix prevents repeated background update actions when the same record is passed to a web component multiple times. It improves reliability and avoids unnecessary duplicate processing in the user interface.

Original PR description

Issue:
If a Component using `useRecordObserver` alternatively received multiple times
the same `record` instances as props, it would have resulted in an `effect`
duplication.

Solution:
Kill the effect based on its associated Promise instead of a boolean shared
between all effects.

#record updates#performance#user interface

[CHG] mail: disable chat hub compact messaging test

PR #200303

Coresaas-18.2mail

This change temporarily disables a failing Mail chat test that was disrupting many staging validation runs. It helps restore confidence in release checks while the underlying issue from a recent change is investigated separately.

#testing#stability#chat

Other(53)

Miscellaneous changes

[FW][FIX] html_editor: ensure text visibility when setting background color

PR #200430

Coresaas-18.2html_editor

**Problem**: When applying a light background color to a table cell, switching to dark mode changes the text color to white, making it invisible. **Solution**: When setting a background color on a block element, also apply the default text color. This ensures text remains visible in both light and dark modes. **Steps to Reproduce**: 1. Add a table. 2. Change the background color of cells to white. 3. Switch to dark mode. 4. Observe that the text inside the cells is not visible. op

Original PR description

**Problem**:
When applying a light background color to a table cell, switching to dark mode changes the text color to white, making it invisible.

**Solution**:
When setting a background color on a block element, also apply the default text color. This ensures text remains visible in both light and dark modes.

**Steps to Reproduce**:
1. Add a table.
2. Change the background color of cells to white.
3. Switch to dark mode.
4. Observe that the text inside the cells is not visible.

opw-4546663

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#196651

Issue: If a Component using `useRecordObserver` alternatively received multiple times the same `record` instances as props, it would have resulted in an `effect` duplication. Solution: Kill the effect based on its associated Promise instead of a boolean shared between all effects.

**Current behavior:** It's possible to end up with a negative valuation for a product with zero product qty. **Expected behavior:** No negative valuation for 0 product qty. **Steps to reproduce:** 1. Create a FIFO, real-time product; create a BOM for fifo-product with some component (tracked by qty, costing method doesn't matter, `standard_price=1`) 2. Purchase 2 units of component @ $1 3. Create and fully process an MO for fifo-prod 4. Change the standard price of component from $1 -> $2 5. Create and fully process a second MO for fifo-prod 6. Unbuild the second MO (from step 5) 7. Sell 1 unit of fifo-prod 8. Check the valuation, see that both the unbuild and out move (sale) use a `unit_cost=$2` despite there having been only 1 qty valued at $2 in the valuation history **Cause of the issue:** SVL creation for fifo costing in an unbuild context does not limit the candidate layer search to moves linked to the actual manufacturing order specified on the unbuild form. So despite us unbuilding the second MO in step 6, the valuation from the first MO's SVL is used. The reason we get the correct `unit_cost` despite using the wrong layer is due to commit: 84dda96 Prior to which, the valuation would have correctly zeroed out but there would have still been this valuation mis-match behind the scenes. **Fix:** Constrain the fifo candidate layer search to finished moves from the unbuilt production (if actuallywhen `_action_confirm`ing unbuild moves. opw-4416350 Forward-Port-Of: odoo/odoo#198499 Forward-Port-Of: odoo/odoo#197190

In commit 2f62d5c0d78371be70586c79cb2b5931e733b042 the issue was fixed for some cases. But the problem remains in some other cases. In the original fix a special context value was added to the reconciliation of some lines. It prevents the creation of cash basis related moves for that reconciliation. This commit adds the same context to all the other reconciliations in the same function as the original reconciliation. Reproduce on runbot for l10n_mx for bank payment method 1. Install l10n_mx 2. Set the 'IVA 16% VENTAS' tax as Customer Taxes on a product. Set the Sales Price to 100. 3. Create a payment method and journal for the PoS * Payment method: Bank on journal BNK1 * Journal: POS 5. Create a PoS using the payment method and journal from the previous step. 6. Start a PoS session 7. Sell the product from step 2 via the Bank payment method. 8. Close the Session 9. The following journal entries will be created: (All the tax lines use the same tax account; the "final" and not the caba transition account) ``` * 1 entry in the POS journal (order) base: | - 100.0 $ tax: | - 16.0 $ receivable: | + 116.0 $ * 1 entry in the BNK1 journal (bank / payment) bank: | + 116.0 $ receivable: | - 116.0 $ * 1 entry in the CBMX journal (caba) base: | - 100.0 $ base: | + 100.0 $ tax: | - 16.0 $ tax: | + 16.0 $ * 1 entry in the EXCH journal (exchange difference) for the cash basis rounding difference tax: | - 16.0 $ tax: | + 16.0 $ ``` opw-4355124 Forward-Port-Of: odoo/odoo#199194

Follow-up of odoo#199828 PR above added a new test that resulted in frequent runbot failures: ``` Failed assertions: 1. [toBe] Failed to find 1 of ".o-mail-ChatHub-compact" with text "1" (Timeout of 3 seconds). Found 0 instead. > Expected: true > Received: false 2. [errors] 1 unverified error(s) Error during test: Failed to find 1 of ".o-mail-ChatHub-compact" with text "1" (Timeout of 3 seconds). Found 0 instead. ``` This happens because the test had a chat window open, enabled the compact mode of chat hub, then posts a message and assert there's a counter on the chathub compact button. Everything works fine when a human do these interactions. However the test failed because there was no counter. This comes from chat window modeling that was thinking the composer was still focused, therefore it was marking the conversation as read, leading to consuming the "1" counter. Composer was kept in "focused" state because when programmatically simulating a `click`, the detection of loss of focus is made with a `focusout` event that is triggered normally on the previously focused element. In HOOT, the `@mail` click test helper was not triggering `focusout` on the previous element. Some attempts were made to programmatically trigger the "focusout", including some reliance of tests that do `mousedown.prevent` that are expected to not change focus on click, but tests keep failing. As this is important to make runbot green as soon as possible, this commit fixes the issue by helping the problematic test to blur/focusout the composer. Note that the `contains().click` from `web_test_helpers` seem to properly managed the focusous and the `mousedown.prevent`, but there are a lot of occurrences of mail `await click()` to change, and this without taking into account some issues in converting to `contains.click()` at the moment: - timeout of click is 200ms, which is too short for discuss tests - mail `click` feature uses `text` to make exact comparison of textnode, compared to `:contains()`. This is probably not a big issue as with `value` where asserting composer is empty asynchronously is very important for discuss The plan is to use web test helpers for mail tests, but this requires more time than the urgency to fix this test now. runbot-159692 Forward-Port-Of: odoo/odoo#200289

*=point_of_sale,pos_restaurant Currently an exception was generated when the user clicked on "Furnitures" in the Choose Your Store section after following the below steps: - Created database without demo and install 'Point of Sale' - Open 'Point of Sale' > Click on "Furnitures" in the Choose Your Store - Archive "Furniture Shop" POS - Click on "Furnitures" in the Choose Your Store - Delete "Furniture Shop" POS - Again, click on "Furnitures" in the Choose Your Store » error generated This is because [1] tries to create a combo product, but it was already created the first time when we loaded data by clicking "furniture", so it generates a validation error from [2] because we cannot link the same product in a combo. This commit solves the above issue by using 'Command.clear()' at [1], which is clear linked combo product before creating it, so it always sets product from data when user loads data. [1] - https://github.com/odoo/odoo/blob/64515f56b3987ffdea6618eb14b6062f95542ac6/addons/product/data/product_demo.xml#L619-L638 [2] - https://github.com/odoo/odoo/blob/64515f56b3987ffdea6618eb14b6062f95542ac6/addons/product/models/product_combo.py#L73 sentry-6101630952 Forward-Port-Of: odoo/odoo#190713

This PR addresses a payslip-calculating issue where overtime records right outside the payslip's period were being included in the calculations, messing up normal hours. The way this is fixed in this PR is by delaying the timezone-stripping code until it is necessary. This allows the local timezone variables, `date_from` and `date_to`, to be used to query the associated overtime records, rather than their UTC versions. We need this behavior because the "overtime" query depends on the field `HrAttendanceOvertime.date`, which is of type `fields.Date` and is timezone-agnostic. This bug can be replicated in any variation of the following scenario (this one assumes the payslip period covers exactly one month of work): - Create an attendance record for employee `A` that would cause them to have `h` hours of overtime at the end of month `X`, where `X` is a number in the set `{1, 2, ..., 12}`. - Create an attendance record for `A` on the 1st of the next month, `Y := X mod 12 + 1`, with `h'` regular hours and `0` hours of overtime. - Generate their payslip for the month `Y`. - See that there is an overtime line with `h` hours and a regular hours line with `h' - h` hours. 🐛 opw-4371083 Forward-Port-Of: odoo/enterprise#80012 Forward-Port-Of: odoo/enterprise#78880

Bug Fixes(2)

[FIX] web: prevent effect duplication for useRecordObserver

[CHG] mail: disable chat hub compact messaging test

Other(53)

[FW][FIX] html_editor: ensure text visibility when setting background color

Bug Fixes(2)

[FIX] web: prevent effect duplication for useRecordObserver

[CHG] mail: disable chat hub compact messaging test

Other(53)

[FW][FIX] html_editor: ensure text visibility when setting background color

[FW][IMP] l10n_mx: new default data for ISR Witheld tax

[FW][FIX] pos_restaurant: show correct time in receipt

[FW][IMP] web: update owl to 2.6.1

[FW][FIX] web: Preserve scroll position in Kanban when loading more data

[FW][FIX] hr_attendance: hide refuse/approve buttons if no extra hours

[FW][FIX] mail: small flicker when expanding avatar stack

[FW] PRHOOT 28

[FW][FIX] mrp{,_account}: constrain fifo candidates for unbuild SVL

[FW][FIX] point_of_sale: register user on residual order

[FW][IMP] mail: return focus back to thread after using quick reactions

[FW][FIX] discuss: add odoo version to rtc logs

[FW][FIX] web: download all attachments of a message in portal

[FW][FIX] sale: combo configurator dialog showing archived products

[FW][FIX] html_editor: hide link button when selection includes blocks

[FW][IMP] l10n_pk, l10n_ae, l10n_eg, l10n_sa, *: Improve Module Descriptions

[FW][FIX] web: avoid saving _original_action on the saved current_action

[FW][FIX] web_editor: removing format doesn't remove font-size

[FW][FIX] html_editor: preserve bullet for image only list item

[FW][FIX] hr_contract: take into account activeness

[FW] Saas 18.1 pos rev lowe

[FW][FIX] mass_mailing{_sms}, project_sms: avoid double tests

[FW][FIX] account: fix switched values in move sending setting

[FW][FIX] account: do not print note / section line placeholders

[FW][FIX] point_of_sale: no caba move during reconciliation

[FW][FIX] crm: fix email alias in action helper

[FW][FIX] mail: no failure ".o-mail-ChatHub-compact" with text "1"

[FW][FIX] product, *: clear product combo before creating product data

[FW][FIX] hr_recruitment: include inactive applications in the application count of the candidate

[FW][FIX] helpdesk: show failed SLA tickets when filters get removed

[FW][FIX] sign,knowledge: set email address to admin user

[FW][IMP] l10n_mx: new default data for ISR Witheld tax

[FW][FIX] account_accountant: Fix wrong rpc call

[FW][FIX] appointment: fix resource on validation page

[FW][FIX] l10n_cz_reports_2025: Properly use SQL formatter

[FW][FIX] knowledge: freeze date for knowledge_calendar_command_tour

[FW] PRHOOT 28

[FW][IMP] l10n_in_reports_gstr: enhance IRN-based bill details fetching

[FW][FIX] account_reports: ignore lines with no name when searching

[FW][FIX] l10n_be_hr_*: fix choose bike behavior

[FW][IMP] l10n_sa_hr_payroll, *, l10n_ae_hr_payroll, *, l10n_pk_reports: Improve module descriptions

[FW][FIX] hr_payroll: timezones messing with overtime

[FW] Saas 18.1 pos rev lowe

[FW][FIX] l10n_it_riba: some followup fixes after client use

[FW][FIX] l10n_ke_edi_oscu: Increase timeout and add logging

[FW][FIX] {website_}appointment_crm: avoid duplicate tests

[FW][FIX] l10n_fr_reports: Update service provider address

[FW][FIX] account_intrastat: prevent copying wrong intrastat code when re…

[FW][FIX] iot: fix Worldline access rights

[FW][FIX] sale_commission: Remove display of bad aggregation in group by

[FW][FIX] pos_tyro: neutralise

[FW][IMP] l10n_uy_edi: Cancel doc if rejected by DGI

[FW][IMP] l10n_co_dian, l10n_co_edi: UBL codes for UoM

[FW][IMP] l10n_sa_hr_payroll, , l10n_ae_hr_payroll, , l10n_pk_reports: Improve module descriptions