Odoo Changelog — 2025-03-13

Thursday, March 13, 2025

38 changes · saas-18.1

Improvements(1)

Enhancements to existing features

[IMP] iot_box_image: change default hostname

PR #201310

Coresaas-18.1iot_box_image

New IoT box images now use “iotbox” as the default device name instead of “raspberrypi.” This makes devices easier to identify as Odoo IoT boxes on a network and reduces confusion with generic Raspberry Pi devices.

Original PR description

Before this commit, the default hostname
of an IoT box was 'raspberrypi'.
After this commit, the default hostname
is now 'iotbox'.

task-4642516

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

#iot#hostname#device identification

Bug Fixes(6)

Resolved issues and error corrections

[FIX] web: no crash on quick open/close of emoji picker

PR #201452

Coresaas-18.1web

This fixes a timing issue that could cause the website editor to crash when users rapidly opened and closed the emoji picker. The change makes the emoji picker handle short-lived loading and closing states more safely, improving editing stability without changing user workflows.

Original PR description

Before this commit, when opening and closing emoji picker quickly, it could crash with the following error: ``` TypeError: Cannot read properties of null (reading 'querySelector') ``` Steps to…

Before this commit, when opening and closing emoji picker quickly, it could crash with the following error:

```
TypeError: Cannot read properties of null (reading 'querySelector')
```

Steps to reproduce:
- Open website editor
- Add a new content block
- In content block, add banner with `/banner`
- spam click quickly on the banner icon

This happens because when clicking very quickly on emoji picker button, the `EmojiPicker` component is in a mounted state and the `gridRef.el` is undefined, thus resulting in the crash when attempting `gridRef.el.querySelector`

The grid has no reason to not be in the template. However, the `useRef()` has a special check to determine whether the ref is attached to DOM, and when not then it returns `null`. The website editor uses web editor, which itself mount the emoji picker in a popover. The click handler closes the popover if it was open and re-opens the emoji picker. Close of popover, when too fast, results to destroying popover before the emoji picker, which detaches the emoji picker from DOM, therefore all refs are `null`. The `EmojiPicker` is about to be destroyed, but for a fraction of time it can re-render itself and access to null refs.

Emoji picker relies heavily on template to model its matrice of emojis for keyboard navigation and managing overflow of
the category navbar. That's why mounting the emoji picker results to 2 renderings. Because of quick mount/unmount, overlay and double rendering of emoji picker, all this puts sometimes the emoji picker in a case of being status "mounted", in a fragment, and calling useEffect to set the active emoji in the grid. This requires `gridRef.el`, which is unfortunately `null` because of being in fragment, thus leading to the crash.

This commit fixes the issue by making the code more defensive against `gridRef.el` not be set, to tackle the case the component is in a fragment while it's being unmounted. `navbarRef.el` could also be `null` for a similar reason but instead of useEffect this is triggered from ResizeObserver.

Other(31)

Miscellaneous changes

[FW][FIX] stock: fix 2 steps delivery customer sublocation

PR #201185

Coresaas-18.1stock

Original PR description

To reproduce:
=============
- create a contact with customer location : Partners/Customer/test
- enable 2 steps delivery on warehouse
- create SO for the contact and confirm it
- validate first step of delivery
- check second step of delivery -> the destination location is Partners/Customer instead of Partners/Customer/test

Problem:
========
Now that we are creating moves step by step we are not passing the destination location to the second move and using the one set on the rule.

Solution:
=========
when creating second move and it's last step we set destination to final destination location.

opw-4374075

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

Forward-Port-Of: odoo/odoo#199278

Before this commit, the default hostname of an IoT box was 'raspberrypi'. After this commit, the default hostname is now 'iotbox'. task-4642516 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Before this commit, when opening and closing emoji picker quickly, it could crash with the following error: ``` TypeError: Cannot read properties of null (reading 'querySelector') ``` Steps to reproduce: - Open website editor - Add a new content block - In content block, add banner with `/banner` - spam click quickly on the banner icon This happens because when clicking very quickly on emoji picker button, the `EmojiPicker` component is in a mounted state and the `gridRef.el` is undefined, thus resulting in the crash when attempting `gridRef.el.querySelector` The grid has no reason to not be in the template. However, the `useRef()` has a special check to determine whether the ref is attached to DOM, and when not then it returns `null`. The website editor uses web editor, which itself mount the emoji picker in a popover. The click handler closes the popover if it was open and re-opens the emoji picker. Close of popover, when too fast, results to destroying popover before the emoji picker, which detaches the emoji picker from DOM, therefore all refs are `null`. The `EmojiPicker` is about to be destroyed, but for a fraction of time it can re-render itself and access to null refs. Emoji picker relies heavily on template to model its matrice of emojis for keyboard navigation and managing overflow of the category navbar. That's why mounting the emoji picker results to 2 renderings. Because of quick mount/unmount, overlay and double rendering of emoji picker, all this puts sometimes the emoji picker in a case of being status "mounted", in a fragment, and calling useEffect to set the active emoji in the grid. This requires `gridRef.el`, which is unfortunately `null` because of being in fragment, thus leading to the crash. This commit fixes the issue by making the code more defensive against `gridRef.el` not be set, to tackle the case the component is in a fragment while it's being unmounted. `navbarRef.el` could also be `null` for a similar reason but instead of useEffect this is triggered from ResizeObserver.

To reproduce: ============= - create a contact with customer location : Partners/Customer/test - enable 2 steps delivery on warehouse - create SO for the contact and confirm it - validate first step of delivery - check second step of delivery -> the destination location is Partners/Customer instead of Partners/Customer/test Problem: ======== Now that we are creating moves step by step we are not passing the destination location to the second move and using the one set on the rule. Solution: ========= when creating second move and it's last step we set destination to final destination location. opw-4374075 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#199278

**Issue:** When printing labels in Dymo format, product reference numbers longer than 10 digits are truncated, resulting in incomplete information. **Steps to Reproduce:** 1. Install the Sales app 2. Navigate to Sales > Products 3. Select or create a product with a reference number longer than 10 digits 4. Click Print Labels > Dynamo format > Confirm 5. Notice that the reference number is cut off after 10 digits Expected Behavior: The full reference number should be visible on the product label, regardless of length Actual Behavior: Reference numbers longer than 10 digits are truncated, showing only the first 10 digits. **Root Cause** The issue arises from a override(https://github.com/odoo/odoo/commit/2b32d1431a33dea9052be3be4f9668a92cd0422e) to the font size of the <small> tag added to Bootstrap. Previously, the font size was set to 0.875em, but it has been updated to 0.8125rem. This change affects text rendering and causes a smaller number of digits to be displayed compared to previous versions. **Fix** To maintain consistency with Odoo 17.0, the font size of the <small> tag is explicitly overridden to ensure the same number of digits is displayed as before. Opw-4578147 Opw-4568804 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#198142

### Issue: Currently, leaving the barcode app will split moves/move lines in the backend in order to keep track of the changes made on the move lines to match the next time you go into the barcode app. #### Use case 1 (split move): - Create a storable product P tracked by lot - Adjust the onHand quantity to put 2 quants in stock: - quant1: Location: WH/Stock, lot_id: LOT0001, quantity: 3.0 - quant2: Location: WH/Stock, lot_id: LOT0002, quantity: 3.0 - Create and confirm a Delivery order for 3 x P > The move of the delivery should have reserved 3 units form LOT0001 - Enter the barcode app, scan you DO-name - Scan your product barcode then scan LOT002 three times - Leave the barcode app and come back #### > The barcode line 3/3 was updated to 3/6: 0/3 LOT001 and 3/3 LOT002. #### Use case 2 (split move line): - Create 2 storable products P and COMP. - Adjust the onHand quantity to put 10 units of COMP in stock. - Create a bill of material for P with one line: - 1 x COMP - Create and confirm an MO for 10 units of P. - Set the qty_producing to 5 units -> 5 units of comp are reserved - Enter the barcode app, scan you MO-name - The component line should be 5/5 since 5 units are reserved. - Adjust the registration to 1/5. - Leave the barcode app and come back #### > The barcode line 1/5 was updated to 1/1 and 0/9 instead of 0/4. ### Cause of the Issue: In both cases, the problem comes from the fact we leave the barcode with a different reservation than the initial one. In the first use case, a new move will be created with a quantity of 3 in order to handle the new line created with LOT002 as soon as you have scanned your products. Therefore even though you entered the barcode app with a reservation demand of 3 units you leave it with 2 move lines with a cumulative quantity of 3 + 3 = 6: - line1: quantity: 3, lot_id: LOT001, picked: False - line2: quantity: 3, lot_id: LOT002, picked: True The next time you enter the app you will therefore see a reservation demand of 6 rather than 3. In the second use case however, a move line is simply created by the `split_uncompleted_moves` when you exit the barcode app: https://github.com/odoo/enterprise/blob/0f4e8ce54be746db02e9f4a6974e387d90608a08/stock_barcode_mrp/models/stock_move.py#L18-L29 And the quantity of the new move line is based on the `prodcut_uom_qty` of the move rather than the initial reservation demand (quantity when entering barcode). This explains why reservation demand changed from 5 to 10 when you left and came back. Enterprise: https://github.com/odoo/enterprise/pull/77068 opw-4353884 and opw-4417870 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#199260 Forward-Port-Of: odoo/odoo#193465

Before this commit all systray items of website were hidden for users that did not have the Restricted Editor right. This commit limits only some of the items to users having the Restricted Editor right: - Published: unrelated - Mobile preview: unrelated - Website switcher: unrelated - + New: Restricted Editor only - Edit in backend: unrelated - Translate: Restricted Editor only - Edit: Restricted Editor only It therefore now shows the Published button only based on the result of the `_compute_can_publish` method of the `website.published.mixin`. The default implementation now checks whether the user has write access to the `website_published` field on the record. Steps to reproduce: - Install `website_crm_partner_assign`. - Connect as a user without any Website role, and in Sales, the "User: Own Documents Only" role. - Go to a partner in the `/partners` page. => "Published" button did not appear. And on the contrary: - Connect as a Restricted Editor user without Sales rights. - Go to a partner in the `/partners` page. - Click on "Published". => An access right error notification did appear. task-3175890 Forward-Port-Of: odoo/odoo#198751 Forward-Port-Of: odoo/odoo#112421

Steps to Reproduce: 1. Create a storable product with inventory tracking and assign a barcode. 2. Create an internal transfer from “Partners/Customers” to “Virtual Locations/Inventory Adjustment”. 3. This will generate two quants, one in Customers and another in Inventory Adjustment. 4. Navigate to Barcode > Inventory Adjustment and scan the product’s barcode. Issue: The scan triggers an inventory adjustment for the “Customer” location instead of the correct stock location. Technical Explanation: • The system fetches all quants related to the product, including those in Vendor, Customer, and Inventory Adjustment locations. • These locations have IDs lower than the stock location (e.g., Customers = 5, Stock = 8). • The front-end caches this data (dbIdCache) and calls _defaultLocation() to determine the location. • Since the cache is ordered by ID, the first location (Customers, ID 5) is incorrectly selected instead of the stock location (8). • As a result, the inventory adjustment is applied to the wrong location. Proposed Fix: • Filter the results to include only internal locations when fetching quants. • This prevents non-internal locations (Vendor, Customers, Inventory Adjustment) from being selected by default. • If a user needs to adjust inventory for an external location, they must first scan the location barcode before scanning the product. Task-4596699 Forward-Port-Of: odoo/enterprise#81107

### Issue: Currently, leaving the barcode app will split moves/move lines in the backend in order to keep track of the changes made on the move lines to match the next time you go into the barcode app. #### Use case 1 (split move): - Create a storable product P tracked by lot - Adjust the onHand quantity to put 2 quants in stock: - quant1: Location: WH/Stock, lot_id: LOT0001, quantity: 3.0 - quant2: Location: WH/Stock, lot_id: LOT0002, quantity: 3.0 - Create and confirm a Delivery order for 3 x P > The move of the delivery should have reserved 3 units form LOT0001 - Enter the barcode app, scan you DO-name - Scan your product barcode then scan LOT002 three times - Leave the barcode app and come back #### > The barcode line 3/3 was updated to 3/6: 0/3 LOT001 and 3/3 LOT002. #### Use case 2 (split move line): - Create 2 storable products P and COMP. - Adjust the onHand quantity to put 10 units of COMP in stock. - Create a bill of material for P with one line: - 1 x COMP - Create and confirm an MO for 10 units of P. - Set the qty_producing to 5 units -> 5 units of comp are reserved - Enter the barcode app, scan you MO-name - The component line should be 5/5 since 5 units are reserved. - Adjust the registration to 1/5. - Leave the barcode app and come back #### > The barcode line 1/5 was updated to 1/1 and 0/9 instead of 0/4. ### Cause of the Issue: In both cases, the problem comes from the fact we leave the barcode with a different reservation than the initial one. In the first use case, a new move will be created with a quantity of 3 in order to handle the new line created with LOT002 as soon as you have scanned your products. Therefore even though you entered the barcode app with a reservation demand of 3 units you leave it with 2 move lines with a cumulative quantity of 3 + 3 = 6: - line1: quantity: 3, lot_id: LOT001, picked: False - line2: quantity: 3, lot_id: LOT002, picked: True The next time you enter the app you will therefore see a reservation demand of 6 rather than 3. In the second use case however, a move line is simply created by the `split_uncompleted_moves` when you exit the barcode app: https://github.com/odoo/enterprise/blob/0f4e8ce54be746db02e9f4a6974e387d90608a08/stock_barcode_mrp/models/stock_move.py#L18-L29 And the quantity of the new move line is based on the `prodcut_uom_qty` of the move rather than the initial reservation demand (quantity when entering barcode). This explains why reservation demand changed from 5 to 10 when you left and came back. Community: odoo/odoo#193465 opw-4353884 and opw-4417870 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#80149 Forward-Port-Of: odoo/enterprise#77068

### Steps to reproduce: - install l10n_ec_edi_pos - Create a new POS in the EC Company. - With a use without inventory adminstrator access rights: - Open a pos session, select any product and a custome linked to the EC localisation. - Try to validate the POS order that is invoiced using the cash payment method. #### > An access error is raised with respect to the `stock_valuation_layer_ids` fields of the account.move model ### Cause of the issue: Clicking on validate will launch a call of the `syncAllOrders` method. During this call, missing records will be fetched recursisvely here: https://github.com/odoo/odoo/blob/2108ad3f7c851eeceb84d7459485a18e1574fa64/addons/point_of_sale/static/src/app/store/pos_store.js#L1271 (Note that this call does not exist prior to 18.0). However, as the data contains a pos order that is related to account moves and since the `account.move` model of the localisation inherit from the `pos.load.mixin`: https://github.com/odoo/enterprise/blob/efa1853cf1f9bbd945a91971ffe40c6906482063/l10n_ec_edi_pos/models/account_move.py#L6-L8 the account move will be fetched as a related record to the pos order and we will launch a `read` for the `fields=[]`: https://github.com/odoo/odoo/blob/2108ad3f7c851eeceb84d7459485a18e1574fa64/addons/point_of_sale/static/src/app/models/data_service.js#L513-L515 https://github.com/odoo/odoo/blob/2108ad3f7c851eeceb84d7459485a18e1574fa64/addons/point_of_sale/models/pos_load_mixin.py#L9-L11 However, a read performed with a false value in the `fields` tries to read the value of each field on the records: https://github.com/odoo/odoo/blob/2108ad3f7c851eeceb84d7459485a18e1574fa64/odoo/models.py#L3792-L3798 This includes protected fields such as the `stock_valuation_layer_ids` that can only be read by user's with administrator stock access rights. opw-4498024 Forward-Port-Of: odoo/enterprise#80156

Improvements(1)

[IMP] iot_box_image: change default hostname

Bug Fixes(6)

[FIX] web: no crash on quick open/close of emoji picker

Other(31)

[FW][FIX] stock: fix 2 steps delivery customer sublocation

Improvements(1)

[IMP] iot_box_image: change default hostname

Bug Fixes(6)

[FIX] web: no crash on quick open/close of emoji picker

Other(31)

[FW][FIX] stock: fix 2 steps delivery customer sublocation

[FIX] web_editor: fix form statusbar overlap in fullscreen

[FIX] mail: correct message reaction placement on websites

[FIX] mail: ensure correct width for deleted message bubble

[FIX] test_appointment_full: adjust performance tests

[FIX] planning: prevent crash on auto deleted recurrencies in cron

[FW][FIX] product: show full reference numbers longer than 10 digits

[FW][FIX] stock_account: added read access right to the stock valuation layer to inv/user group

[FW][FIX] spreadsheet: download button in topbar menu of shared spreadsheet

[FW][FIX] stock_barcode{,_mrp}: reconcile splitted move from barcode exit

[FW][FIX] website_event_booth: adapt for stable view changes

[FW][FIX] project: only compute duration tracking when project stage feature enabled

[FW][FIX] l10n_dk: check if tax exists

[FW][FIX] mail: add debounce on fetchToPartnerInvite

[FW][FIX] point_of_sale: added rounding to 2 decimals on product card

[FW][FIX] account: don't create unaffected if already exist

[FW][FIX] l10n_es_edi_sii: allow back modification

[FW][FIX] website_sale_collect: remove unnecessary override

[FW][FIX] account: payment date not updating move date

[FW][FIX] l10n_ro_edi_stock: conditionally checking if the module is installed

[FW][FIX] website: allow publishing without relying on Restricted Editor

[FW][FIX] l10n_in_ewaybill_stock: Missing tax detail for intra state

[FW][IMP] account,base_vat: company registry placeholders

[FW][FIX] portal: prevent error when salesperson has no email

[FW][FIX] stock_barcode: Ensure Correct Location for Inventory Adjustment via Barcode

[FW][FIX] account_sepa: allow non IBAN for ISO 20022

[FW][FIX] sale_subscription: Apply good email template on subscription

[FW][FIX] sale_subscription: Correcting wrong deadline for recurring goods

[FW][FIX] sale_commission: fix commission by team

[FW][FIX] l10n_cl_edi_factoring: add a special parser method to prevent errors

[FW][FIX] stock_barcode{,_mrp}: reconcile splitted move from barcode exit

[FW][FIX] l10n_ec_edi_pos: allow pos user to validate a pos order

[FW][FIX] l10n_ch_hr_payroll_elm_transmission: Fix access right issue

[FW][FIX] l10n_mx_edi_extended: ValorUnitarioAduana wrong

[FW][FIX] web_studio: runbot-error-111977

[FW][IMP] pos_urban_piper: add rappi provider