Daily updates from Odoo
Sunday, May 24, 2026
13 changes
2 changes
Resolved issues and error corrections
This update fixes issues with website translations, specifically addressing formatting errors like trimmed spaces and incorrect text preservation. It also enhances the translation process by supporting metadata attributes and preventing duplicate translation requests, ensuring more accurate and reliable website content for all users.
Original PR description
This commit fixes and improves several aspects of the recently merged [translate the whole page]. - Fix formatting issues in the translation like: - Space getting removed while translating - Meaning…
This commit fixes and improves several aspects of the recently merged
[translate the whole page].
- Fix formatting issues in the translation like:
- Space getting removed while translating
- Meaning of text is not preserved after translation.
- Example :
- 'Enhance Your' and '<b>Experience</b>' becomes, 'Enhance Your<b>Enhance Your Experience</b>'
- 'hello <b>world</b>' becomes 'Hola<b>mundo</b>' space is trimmed.
- Exclude non-translatable elements such as `.o_brand_promotion` from
translation.
- Support metadata translation, ensuring that translatable attributes
are correctly handled (`alt`, `title`, `placeholder`, and `value`
attributes).
- Disable the “Translate” button while the translation process is
running to prevent multiple concurrent requests.
[translate the whole page]: https://github.com/odoo/odoo/commit/6e1e359ec6a7ae23cfa7d7c96380f845c7fdcfe5
task-5047714
Forward-Port-Of: odoo/odoo#266260
Forward-Port-Of: odoo/odoo#229894This change improves performance by avoiding redundant queries when retrieving account statements. Specifically, it eliminates unnecessary queries based on name and statement line matching, reducing database load and improving response times. This enhancement focuses on efficiency without altering core functionality.
Original PR description
Various improvements related to performance for `<account.bank.statement.line>._retrieve_partner` Forward-Port-Of: odoo/enterprise#118267 Forward-Port-Of: odoo/enterprise#117738
2 changes
Resolved issues and error corrections
This update enhances the website translation process by fixing formatting issues like trimmed spaces and preserving text meaning. It also improves the handling of metadata attributes (alt, title, etc.) and prevents multiple translation requests, ensuring more accurate and reliable translations across the Odoo website.
Original PR description
This commit fixes and improves several aspects of the recently merged [translate the whole page]. - Fix formatting issues in the translation like: - Space getting removed while translating - Meaning…
This commit fixes and improves several aspects of the recently merged
[translate the whole page].
- Fix formatting issues in the translation like:
- Space getting removed while translating
- Meaning of text is not preserved after translation.
- Example :
- 'Enhance Your' and '<b>Experience</b>' becomes, 'Enhance Your<b>Enhance Your Experience</b>'
- 'hello <b>world</b>' becomes 'Hola<b>mundo</b>' space is trimmed.
- Exclude non-translatable elements such as `.o_brand_promotion` from
translation.
- Support metadata translation, ensuring that translatable attributes
are correctly handled (`alt`, `title`, `placeholder`, and `value`
attributes).
- Disable the “Translate” button while the translation process is
running to prevent multiple concurrent requests.
[translate the whole page]: https://github.com/odoo/odoo/commit/6e1e359ec6a7ae23cfa7d7c96380f845c7fdcfe5
task-5047714
Forward-Port-Of: odoo/odoo#266216
Forward-Port-Of: odoo/odoo#229894This update fixes an issue where the search bar dropdown was partially obscured by snippet blocks on the /shop page. The fix dynamically adjusts the layout to ensure the dropdown is always visible, improving the user experience when browsing products. This ensures all search results are displayed correctly.
Original PR description
On /shop, when a snippet block sits above the searchbar, the search dropdown was rendered partially hidden behind that block (cropped/unreadable items). Steps to reproduce: =================== 1. Go…
On /shop, when a snippet block sits above the searchbar, the search dropdown was rendered partially hidden behind that block (cropped/unreadable items). Steps to reproduce: =================== 1. Go to /shop. 2. Add a snippet block above the searchbar. 3. Type in the searchbar. => Observed: search results appear cropped, with upper items hidden behind the snippet block above. Root cause: =========== the products grid column (`#products_grid`) has `overflow: auto`, https://github.com/odoo/odoo/blob/d9bb1c1dc90f97b63b87ad762fc4ab36abf7e05f/addons/website_sale/static/src/scss/website_sale.scss#L442 which clips any absolutely-positioned descendant that extends past its bounds. The dropdown's containing block is the searchbar `<form>` (position: relative), which lives inside that column. When the dropdown grew (or flipped to dropup) and extended outside the column, the part outside was clipped, and any positioned snippet siblings above the column painted over the clipped area. Fix: ====== while the dropdown is mounted, lift the `overflow: auto` on its ancestor `div.col` so the menu can extend past the column and paint on top of other content. Done from JS so no SCSS rule has to target the searchbar-specific column. opw-6216317 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#265982 Forward-Port-Of: odoo/odoo#265558
1 change
Resolved issues and error corrections
This update resolves an issue preventing proper session closure with Fiskaly cash register transactions. The system was incorrectly removing internal capital letters from cash move types (like 'ZuschussEcht'), leading to a mismatch with Fiskaly's requirements. This fix ensures accurate data exchange with the Fiskaly system.
Original PR description
Fiskaly cash register move types must match the keywords listed in the documentation: https://developer.fiskaly.com/dsfinvk/process_types_business_transaction_types#business-transaction-types-business-cases Some values are camelCase (e.g. ZuschussEcht) and are set in the frontend as zuschussEcht. Using capitalize() removes internal capital letters, causing a mismatch with Fiskaly expectations and preventing session closing. Steps to reproduce: - Set up Fiskaly - Open a PoS session - Add an "in" cash move with category Cash Supplement - Create and validate an order - Close the session opw-6165687 Forward-Port-Of: odoo/enterprise#115438
1 change
Resolved issues and error corrections
This update resolves a technical issue preventing proper communication with Fiskaly, a key payment processor. The system was incorrectly removing internal capital letters from cash register move types, leading to errors and preventing session closure. This fix ensures accurate data transfer to Fiskaly, maintaining seamless operations.
Original PR description
Fiskaly cash register move types must match the keywords listed in the documentation: https://developer.fiskaly.com/dsfinvk/process_types_business_transaction_types#business-transaction-types-business-cases Some values are camelCase (e.g. ZuschussEcht) and are set in the frontend as zuschussEcht. Using capitalize() removes internal capital letters, causing a mismatch with Fiskaly expectations and preventing session closing. Steps to reproduce: - Set up Fiskaly - Open a PoS session - Add an "in" cash move with category Cash Supplement - Create and validate an order - Close the session opw-6165687 Forward-Port-Of: odoo/enterprise#115438
1 change
Resolved issues and error corrections
This update resolves an issue preventing proper session closure with Fiskaly by ensuring that cash register move types are handled correctly. Specifically, the system now recognizes camelCase values (like 'ZuschussEcht') as they are entered, aligning with Fiskaly's requirements and avoiding errors.
Original PR description
Fiskaly cash register move types must match the keywords listed in the documentation: https://developer.fiskaly.com/dsfinvk/process_types_business_transaction_types#business-transaction-types-business-cases Some values are camelCase (e.g. ZuschussEcht) and are set in the frontend as zuschussEcht. Using capitalize() removes internal capital letters, causing a mismatch with Fiskaly expectations and preventing session closing. Steps to reproduce: - Set up Fiskaly - Open a PoS session - Add an "in" cash move with category Cash Supplement - Create and validate an order - Close the session opw-6165687 Forward-Port-Of: odoo/enterprise#115438
5 changes
Resolved issues and error corrections
This update corrects a translation issue within the Odoo Enterprise Gantt view. The button used to toggle display modes was not properly translated, preventing users from seeing the view in their preferred language. This fix ensures all users can consistently access and utilize the Gantt view in their local language.
Original PR description
The title of the button allowing to toggle the display mode in the Gantt view was not translated. This commit adds a getter to compute the title based on the current display mode, and uses it in the template. Issue reported by translator. Forward-Port-Of: odoo/enterprise#118173 Forward-Port-Of: odoo/enterprise#117739
This update resolves an issue where US companies were missing Avatax fiscal positions. The system now correctly creates these positions based on the specific country's CoA, and also incorporates Canada. This ensures accurate tax reporting for our US and Canadian clients.
Original PR description
The fiscal position was being created specifically for countries using the Generic CoA. This stems from before the US had its own CoA [1]. Because of this, US companies no longer had an Avatax fiscal position created for them. Now that the US has its own CoA, we move to a simpler `@template()` approach and take the opportunity to add Canada as well. [1] odoo/odoo#223745 task-6228639 Forward-Port-Of: odoo/enterprise#117966
This update removes a redundant process for translating embedded actions in Odoo. Previously, a manual translation step was required, but now that embedded actions automatically inherit translations from their linked actions, this step is no longer necessary. This streamlines the process and ensures consistent translations.
Original PR description
Now that `ir.embedded.actions` delegates its display name to the linked action, the manual translation copy on embedded action creation is no longer needed. Related: https://github.com/odoo/odoo/pull/262981 Forward-Port-Of: odoo/enterprise#117772 Forward-Port-Of: odoo/enterprise#116369
This update resolves a test failure in the Odoo WhatsApp app's discuss sidebar. The change ensures the test accurately reflects the new system behavior of only considering active users when determining user IDs. This improves the reliability of the test and ensures the app functions correctly for users.
Original PR description
This PR updates the discuss sidebar testcase to match the new behavior where only active users are considered when computing main_user_id, reducing the number of available commands and fixing the failing assertion. community: https://github.com/odoo/odoo/pull/262247 task-6179486 Forward-Port-Of: odoo/enterprise#118063 Forward-Port-Of: odoo/enterprise#117480
This update ensures that quality checks are displayed only for the products actually picked within a stock picking. Previously, all products associated with a picking would trigger quality checks, even if only one was picked. This change improves efficiency and prevents unnecessary quality check generation.
Original PR description
*: stock_barcode_quality_control Issue --------------------------------- When a picking contains multiple products and each product has its own operation-type quality point, opening the Quality…
*: stock_barcode_quality_control Issue --------------------------------- When a picking contains multiple products and each product has its own operation-type quality point, opening the Quality Checks from the button shows all quality checks, even for only one product is picked yet. However, when validating the picking directly, only the picked products' quality checks are shown. Steps to reproduce --------------------------------- - Create two products (Product A, Product B) - Create one quality point per product with operation type and product_id set - Create a receipt including both products - Picked only Product A - Click on the "Quality Checks" button - Quality checks for both products are displayed instead of only Product A. Cause --------------------------------- The Quality Checks button uses `_is_checkable`, which calls `_is_checkable_from_context`. This method always returns True unless the context contains 'picking_validation'. That context key is only set during the validation flow, so the button flow incorrectly shows all checks. With this commit: --------------------------------- Remove the unnecessary context-based condition and align the logic so that both the Quality Checks button and the validation flow only consider picked products. Quality checks opened from the button or validation now behave consistently and only include checks for products that are actually picked, preventing irrelevant or premature quality checks. Task ID: 4647113
1 change
Resolved issues and error corrections
This update resolves an issue preventing proper communication with Fiskaly, our point-of-sale integration. The system was incorrectly removing internal capital letters from cash register move types (like 'ZuschussEcht'), causing a mismatch with Fiskaly's requirements and preventing session closures. This fix ensures our system correctly handles these types, maintaining compatibility with the Fiskaly platform.
Original PR description
Fiskaly cash register move types must match the keywords listed in the documentation: https://developer.fiskaly.com/dsfinvk/process_types_business_transaction_types#business-transaction-types-business-cases Some values are camelCase (e.g. ZuschussEcht) and are set in the frontend as zuschussEcht. Using capitalize() removes internal capital letters, causing a mismatch with Fiskaly expectations and preventing session closing. Steps to reproduce: - Set up Fiskaly - Open a PoS session - Add an "in" cash move with category Cash Supplement - Create and validate an order - Close the session opw-6165687 Forward-Port-Of: odoo/enterprise#115438