Daily updates from Odoo
Wednesday, April 29, 2026
9 changes · saas-18.3
Resolved issues and error corrections
This update resolves an issue where power buttons were incorrectly displayed and overlapping other menu items within the HTML editor, particularly on smaller screens. The fix adjusts the editor's display based on its own width, ensuring buttons are hidden when they cause overlap, improving the user experience.
Original PR description
Problem: Power buttons are shown regardless of the editor field's actual rendered width, causing them to overlap other menus when the field is small. Solution: Instead of relying solely on the global…
Problem: Power buttons are shown regardless of the editor field's actual rendered width, causing them to overlap other menus when the field is small. Solution: Instead of relying solely on the global `ui.isSmall` (mobile detection), check the editor field's own width and hide power buttons whenever it falls below the overlap threshold. Before: <img width="576" height="301" alt="image" src="https://github.com/user-attachments/assets/dcebed55-5c80-4fe5-8d33-c320549cf347" /> After: <img width="542" height="336" alt="image" src="https://github.com/user-attachments/assets/34a233bb-9958-43ac-adb9-04702a2e403d" /> Steps to reproduce: - Change languange (French to have a long placeholder). - Settings > Customer Invoices > Default Terms & Conditions. - Check "Add a Note". - Resize the screen to smaller size. - Observe the power buttons overlap with the translate button. task-6117734 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#259094
This update corrects an issue where signatures were incorrectly duplicated on generated sales order PDFs after modification. Moving forward, signatures will only be printed on documents created directly by the signature process, ensuring consistency and accuracy in sales order documentation. This change enhances the reliability of our sales order generation.
Original PR description
A signed order can be modified afterward while retaining the signature on the newly generated PDF. After this commit, we will only print the signature on the document generated by the signature itself and not on any generated PDF afterwards. opw-6159170 Forward-Port-Of: odoo/odoo#261288
This update fixes an error in the Datev general ledger export that resulted in incorrect tax rates being reported. The issue stemmed from how multiple tax repartition lines were handled, leading to amounts being replaced instead of added. This ensures accurate tax reporting for Datev customers.
Original PR description
With l10n_de_reports: - Configure a foreign currency with an exchange rate. - Configure a tax with multiple repartition lines. - Create a vendor bill in this foreign currency with this tax. - In the general ledger export the datev csv. In the datev csv the rate is wrong. In the method _l10n_de_datev_get_csv, we build a tax_amount dict. However when one tax has multiple lines, the amount is replaced and not added. opw-6010097 Forward-Port-Of: odoo/enterprise#110453
This update corrects an issue where the Partner Ledger displayed incorrect initial balances when the date range filter wasn't used. The fix ensures that the total balance aligns with the sum of all invoices, providing more accurate financial reporting for partners. This improves the reliability of our accounting data.
Original PR description
To reproduce the issue: 1) Create an invoice of 100 € for partner A in 2025 2) Create another invoice of 200€ for the same partner in 2026 3) Open the Partner Ledger for 2026. Unfold A. It shows an initial balance of 100€ and a total of 300€. 4) In debug mode, open the Partner Ledger's form view and uncheck the date range option. 5) Open the Partner Ledger like in step 3) ====> An initial balance of 300€ shows, making the total of Partner A (still 300€) inconsistent with the sum of its sublines (600€) feedback-6042305 Forward-Port-Of: odoo/enterprise#115455
This update resolves an issue where unit prices were not being rounded correctly when generating Peppol invoices. This fix ensures accurate pricing information is included in invoices, improving compliance with Peppol standards and preventing potential discrepancies in financial reporting. The change reverts a previous commit that introduced this error.
Original PR description
This reverts commit d19223a148ab3476b83ed71346eb0712394b7de7. Forward-Port-Of: odoo/odoo#261941
A small update has replaced the previous video used in the website's editing interface with a new, available video. This ensures the website's video snippets continue to function correctly and avoid any display issues caused by the original video no longer being accessible. This is a routine maintenance fix.
Original PR description
Specification: - The previously embedded video used by the "s_video" snippet (id=G8b4UZIcTfg) is no longer publicly available. After this commit: - This commit replaces the default video with a new publicly available one (id=nbso3NVz3p8). task-6034987 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#261064 Forward-Port-Of: odoo/odoo#253874
This update fixes an issue where users without write access to the Point of Sale (PoS) in the AT (Austria) version of Fiskaly would receive an access error when attempting to authenticate after a token expiration. The fix ensures that users are correctly denied access, preventing errors and improving the PoS experience for AT business customers.
Original PR description
When trying to auth directly from the PoS when the token expires, if you are logged in with a user that doesn't have write access to the PoS. You would get an access error. Steps to reproduce: ------------------- * Setup Fiskaly in an AT company * Open PoS and try to make a sale * To fake the token expiration I modified the code so that the request always return 401 status code > Observation: You get an access error opw-5925203
This update fixes a bug where users without the necessary permissions were encountering errors when trying to access their profile information. The team added a specific field to the user data to ensure that all users can view their own profile details, regardless of access rights. This improves the user experience and prevents frustration.
Original PR description
Issue: - When a user without access rights tries to view their profile, a permission error is raised. - Issue PR: https://github.com/odoo/odoo/pull/254162 Fix: - Added `employee_country_code` to SELF_READABLE_FIELDS in `res.users`. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#255260
This update corrects inaccurate help text for employee fields within the Point of Sale (PoS) module. The previous text was misleading, stating that all employees could log in if the lists were empty. This change ensures the help text accurately describes the purpose of each field – minimal and basic employee selections – improving clarity for users.
Original PR description
Both `minimal_employee_ids` and `basic_employee_ids` had the same incorrect help text ("If left empty, all employees can log in to PoS"), which did not reflect the actual purpose of each field. The condition also only holds when all three employee lists are empty, not per-field.
opw-6171362
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr