Daily updates from Odoo
Navigate
Branch
Saturday, September 20, 2025
7 changes
1 change
Resolved issues and error corrections
This fix prevents an error when a user presses the up arrow while editing an empty message that only contains an attachment. The message composer now stays stable in this edge case, reducing interruptions for users working with attachments in discussions.
Original PR description
**Description of the issue this PR addresses:** ------------------------------------------------ Pressing the ArrowUp key in the editing composer when it is empty while editing a message with only an…
**Description of the issue this PR addresses:** ------------------------------------------------ Pressing the ArrowUp key in the editing composer when it is empty while editing a message with only an attachment caused a JavaScript traceback. This happened because the composer was not associated with a thread, and the code tried to access `composer.thread.lastEditableMessageOfSelf`. **Current behavior before PR:** --------------------------------- - Pressing ArrowUp in the empty editing composer triggers a TypeError - The error occurs when editing a message that only has an attachment - The composer does not have a thread reference **Desired behavior after PR is merged:** ----------------------------------------- - Pressing ArrowUp in this scenario safely checks if a thread exists - No TypeError occurs, and the composer remains stable **Task:** 5068553 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#227673
1 change
Resolved issues and error corrections
Fixed an issue where using the Translate action on messages from a mobile device could cause an error instead of showing the translated message. This improves reliability for users reading and responding to chatter messages on mobile.
Original PR description
Steps to reproduce: - Open any chatter with a message on mobile - Try to translate the message using the Translate mobile action => Throws traceback This happens because the component here is `MessageActionMenuMobile` instead of `Message`, and MessageActionMenuMobile does not have the `onClickToggleTranslation` method. This PR fixes the issue. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#227242 Forward-Port-Of: odoo/odoo#223567
1 change
Resolved issues and error corrections
Field Service task forms now show the repeat interval directly under the planned date. This makes recurring task scheduling easier to find and understand, reducing confusion when setting up or reviewing service visits.
Original PR description
**Steps to Reproduce:** 1. Open the Field Service app. 2. Create or open an existing task. 3. Check the form view of the task. **Issue:** - The 'Repeat Every' block was displayed at the bottom of the sheet, making it less intuitive. - It should logically appear under the 'Planned Date' block for better visibility. **Current behaviour:** - The 'Repeat Every' block appears in a different section, away from the 'Planned Date' block. **Expected behaviour:** - The 'Repeat Every' block should be displayed directly under the 'Planned Date' block for better usability and logical grouping. **Fix:** - Adjusted the form view XML to move the 'Repeat Every' field below the 'Planned Date' field. **Task-5040281** Forward-Port-Of: odoo/enterprise#95098 Forward-Port-Of: odoo/enterprise#93208
3 changes
Resolved issues and error corrections
This fixes a display issue in the Mail Threads panel where some thread previews appeared too narrow instead of filling the available space. Users now get a cleaner and more consistent view when browsing conversation threads.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/227734 PR above made an improvement to display thread preview below message that initiated these threads. This PR introduced a style regression in thread list: some thread previews in the thread list in the "Threads" action panel were not taking the whole width, which this commit fixes. Before <img width="483" height="302" alt="Screenshot 2025-09-20 at 12 48 02" src="https://github.com/user-attachments/assets/daaec1cc-d57b-414a-aa47-b9db9d720596" /> After <img width="483" height="303" alt="Screenshot 2025-09-20 at 12 48 13" src="https://github.com/user-attachments/assets/285c2d2d-d79b-4db6-b808-e046cb152e73" />
This fix prevents an error when users press the up arrow while editing an empty message composer for a message that only contains an attachment. The message editor now stays stable, avoiding an unnecessary interruption in the mail workflow.
Original PR description
**Description of the issue this PR addresses:** ------------------------------------------------ Pressing the ArrowUp key in the editing composer when it is empty while editing a message with only an…
**Description of the issue this PR addresses:** ------------------------------------------------ Pressing the ArrowUp key in the editing composer when it is empty while editing a message with only an attachment caused a JavaScript traceback. This happened because the composer was not associated with a thread, and the code tried to access `composer.thread.lastEditableMessageOfSelf`. **Current behavior before PR:** --------------------------------- - Pressing ArrowUp in the empty editing composer triggers a TypeError - The error occurs when editing a message that only has an attachment - The composer does not have a thread reference **Desired behavior after PR is merged:** ----------------------------------------- - Pressing ArrowUp in this scenario safely checks if a thread exists - No TypeError occurs, and the composer remains stable **Task:** 5068553 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#227673
Documentation and clarification updates
This pull request records that contributor noelibon has signed Odoo's Individual Contributor License Agreement. This is a legal documentation update that helps ensure future contributions can be accepted under Odoo's licensing requirements.
Original PR description
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
1 change
New functionality added to Odoo
This change adds a safer way for developers to extend existing view settings without replacing them entirely. It reduces the risk of accidental configuration loss when adapting screens, helping customizations remain more reliable during upgrades and maintenance.
Original PR description
This commit introduces a new `merge` attribute to the `<attribute>` tag, allowing developers to safely merge existing dictionary-based or list-based attributes in XML view inheritance. Problem:…
This commit introduces a new `merge` attribute to the `<attribute>` tag, allowing developers to safely merge existing dictionary-based or list-based attributes in XML view inheritance.
Problem:
Currently, when a developer needs to extend an attribute like `options` or `domain` in an inherited view, they must completely redefine the attribute, which can lead to unintended overwrites of properties set in the base view. For example, to add a new option, one must copy all existing options, which is tedious and brittle.
Solution:
The new `merge` attribute provides a declarative way to extend these attributes. When specified on an `<attribute>` tag, it intelligently merges its value with the existing attribute value on the target node. For dictionary-based attributes like `options`, it performs a dictionary update. For list-based attributes like `domain`, it extends the list.
Usage Example:
Given an existing field with a base `options` attribute: `<field name="supplier_id" options="{'no_open': 1, 'no_create': 1}"/>`
A developer can now extend this in an inherited view without overwriting: `<attribute name="options" merge="{'list_view_ref':'cm_product.cm_product_supplierinfo_tree_view'}"/>`
The result will be a combined `options` attribute: `options="{'no_open': 1, 'no_create': 1, 'list_view_ref': 'cm_product.cm_product_supplierinfo_tree_view'}"`
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