Daily updates from Odoo
Saturday, January 24, 2026
12 changes · master
Resolved issues and error corrections
This update resolves a problem where image transformations were incorrectly applying translations, leading to misaligned images. Removing the translate feature during image transformation ensures accurate resizing and rotation, improving image display quality. The change also updates icons to reflect the removal of translation functionality.
Original PR description
*: `html_builder` In website, the translate feature while transforming an image can occur issues or misleading. This PR aims to remove translate feature from image transformation. task-5190342 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update enhances the portal user experience by automatically scrolling to the specific message when a linked message is opened. Previously, clicking a message link only opened the record, making it harder to quickly view the content. This change improves usability and efficiency for portal users.
Original PR description
*= website_slides, website_sale, test_mail_full **Current behavior before PR:** Opening a copied message link does not automatically scroll to the message for portal users, it only opens the record. **Desired behavior after PR is merged:** Opening the copied link now automatically scrolls to the specific message within the record instead of just opening the record. task-id:[4518058](https://www.odoo.com/odoo/project/1519/tasks/4518058) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves a technical issue that was causing tests to fail due to dynamic date usage. The test now utilizes a freeze-time mechanism, ensuring consistent and reliable test results. This change improves the stability and reliability of the employee version timeline feature.
Original PR description
As runbot faketimes test fail because the usage of dynamic dates now the test uses freeze_time Task#5717031 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#244540
This update adds a 'Reload Data' button to error dialogs in the Point of Sale system, providing users with a simple way to resolve common issues. This reduces downtime and frustration by allowing quick data recovery, especially for Restaurant orders which now attempt to sync before reloading.
Original PR description
Purpose: ------------ - On Error dialogs, users only had "Ok" or could close the dialog, with no guidance on what to do next. - Many blocking issues are resolved simply by reloading POS data. Before this commit: ----------- - Error dialogs only had an "Ok" button. After this commit: ------------------ - Added a "Reload Data" button for quick recovery of common blocking issues. - Added a warning message in the reload data popup - For POS Restaurant, orders will attempt to sync before reloading data, reducing the risk of data loss. Task-5353590 Forward-Port-Of: odoo/odoo#244321 Forward-Port-Of: odoo/odoo#238112
This update fixes an issue where clicking links within the Odoo chat window on mobile devices caused the chat window to remain open and block the new page from appearing. The change now automatically folds the chat window after a link click, ensuring users can easily view the linked page. This enhances usability and prevents frustration for mobile users.
Original PR description
Clicking on an odoo link in the chat window will take the user to the related page in odoo. However, in mobile view, the chat window remains unfolded and covers the entire page, so the user can't see the newly opened page below the chat window unless they fold the chat window. This change fixes this by folding the chat window in mobile view when clicking an odoo link inside the chat window. task-4762503 Forward-Port-Of: odoo/odoo#244905 Forward-Port-Of: odoo/odoo#208440
This update fixes an issue where employee names were being incorrectly formatted in payroll reports (specifically, last name before first name). The code has been corrected to ensure names are consistently displayed as 'FirstName LastName,' aligning with Swiss regulations and improving report accuracy. Test data has also been updated to reflect this change.
Original PR description
* Fix _compute_l10n_ch_legal_name method to correctly assign first_name and last_name from employee name (was previously reversed) * Update all SwissDEC test data to use correct "FirstName LastName" format instead of "LastName FirstName" to match the corrected computation logic task-5102851 Forward-Port-Of: odoo/enterprise#105044 Forward-Port-Of: odoo/enterprise#95252
This update strengthens Odoo's database safety by ensuring that queries against PostgreSQL always use the correct schema. This prevents potential errors and data corruption that could occur when multiple schemas are used simultaneously, addressing a previously reported issue. It's a proactive measure to maintain data integrity and stability.
Original PR description
Safety measure to prevent hidden bugs and data corruption which can happen when multiple schema are used in PostgreSQL. Description of the issue/feature this PR addresses: Related to: - PR #243833 - OPW [opw-5495025](https://www.odoo.com/my/tasks/5495025) - issue reported earlier: #97891 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#243967
This update resolves an issue where the map component wasn't displaying correctly within the Odoo Studio. The fix addressed a missing size constraint, allowing the map to render. However, the map remains non-interactive, indicating a separate problem that needs attention.
Original PR description
Before this commit, the map did not render in studio. This was because the container did not have a size. After this commit, the map renders correctly, but it is still not clickable or interactable. task-5432169 Forward-Port-Of: odoo/enterprise#104968 Forward-Port-Of: odoo/enterprise#104114
This update corrects a bug in the Master Production Schedule (MPS) that caused excessive component reordering for kit products. Specifically, a calculation error resulted in the system ordering components in exponential amounts. This fix ensures accurate replenishment and prevents overstocking of components when ordering kits through the MPS.
Original PR description
***Behavior:*** In a setting with a second warehouse that is supplied by the first one. Creating a product that uses that ressuply route, and then adding it to the bom of a kit product will make it…
***Behavior:*** In a setting with a second warehouse that is supplied by the first one. Creating a product that uses that ressuply route, and then adding it to the bom of a kit product will make it so that when ordering the kit product to the second warehouse from the MPS, the system will create an order for an exponential amount of components. When calling action_replenish, kit products for which the components don't have an MPS entry will have their product_ratio computed to know how many components to reorder. However the current formula is wrong or outdated and ends up returning the squared amount. ***Steps to reproduce:*** - Create a second warehouse. - Check Resuply From 'First Warehouse' (this will unarchive a route) - Create a product that uses that route for reordering. - Create a second product - Create a kit for that product BOM composed of the first product make sure the amount of component is more than 1 - In the Master Production Schedule: Add the kit product and make sure it is produced in the second warehouse with the unarchived route. - Add any amount to reorder in 'Replenishment' then click the Order button. - If you go to deliveries and look for your component, you'll see the amount of component per kit squared multiplied by the reordered kit amount. opw-5351460 Forward-Port-Of: odoo/enterprise#101462
This update fixes a display issue in the spreadsheet filter side panel. Field matching is now only shown after a model and field have been selected, aligning with other filter types. This ensures a more intuitive and consistent user experience for configuring spreadsheet filters.
Original PR description
## Description Before this commit: - In the selection global filter side panel, field matching was shown immediately, even when the model and field were not selected. - Without a model, field matching cannot be configured correctly, so showing it early had no meaning. - This behavior was inconsistent with relational global filters. After this commit: - Field matching is displayed only after the user selects both model and field. - Once configured, users can set up field matching as expected, similar to the relational global filter side panel. Task: [5477251](https://www.odoo.com/odoo/project/2328/tasks/5477251) Forward-Port-Of: odoo/enterprise#104545
This update resolves an issue where tables inserted into the To-Do editor appeared after the existing text instead of before it. The fix streamlined the table insertion process, ensuring tables are now correctly placed at the beginning of the block where the user intended. This improves the overall user experience and consistency within the editor.
Original PR description
### Steps to Reproduce : - Open To-Do and type some text. - Place the cursor at the start of the block. - Insert a table. (e.g.: /table) - The table appears after the text instead of before it. ### Purpose of this PR: - Table insertion logic was previously duplicated inside TablePlugin, where it tried to manually split text and inline nodes before inserting the table. However, this responsibility is now correctly handled by `DomPlugin.insert()`, which already: - deletes the current selection if needed. - splits text and inline nodes safely. - handles block boundaries and unsplittable elements. - normalizes the DOM after insertion. - places the cursor at a valid position. task-5480759 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#244689 Forward-Port-Of: odoo/odoo#243242
This update corrects a test failure related to how dates and times are displayed in Chrome. A recent change introduced a regular space instead of a non-breaking space, causing compatibility issues. This fix ensures consistent date and time formatting across different Chrome versions.
Original PR description
Apparently somewhere in the datetime patterns the space between time and A/P mark has been updated from a narrow non-breaking space to a regular space. Make the code cross-version compatible. Forward-Port-Of: odoo/odoo#244961