Daily updates from Odoo
Saturday, April 4, 2026
25 changes
7 changes
Resolved issues and error corrections
This update corrects a technical issue in the l10n_be_intervat module, ensuring it aligns with a recent change in Odoo's configuration system. Specifically, the module now uses the correct method (get_str) for retrieving configuration parameters, improving stability and compatibility with the latest Odoo version (19.2).
Original PR description
Since 19.1, ir.config_parameter.get_param is replaced by get_str. This commit fix a mistake I made in the forward port of https://github.com/odoo/enterprise/pull/112719 no-task Forward-Port-Of: odoo/enterprise#112979
This update clarifies how the system handles electronic invoices from Uruguay. Specifically, it prevents ‘e-Cobranza’ documents (which are more like receipts) from being incorrectly synchronized as vendor bills. This ensures data consistency and aligns with how other related documents are processed.
Original PR description
This pull request improves the synchronization process of vendor bills within the Uruguayan localization (`l10n_uy_edi`). Currently, the system might fetch documents that are not technically bills during synchronization. With this change, the system will explicitly avoid synchronizing `e-Cobranza` (Collection notes or Receipts) documents as vendor bills. Reasoning: `e-Cobranza` documents function conceptually more like payment receipts rather than actual vendor bills. Pulling them into the system as bills creates inconsistencies. This update aligns the handling of `e-Cobranza` with the existing behavior for `e-Remito` (Delivery Guides) and `e-Resguardos` (Withholdings), which are also appropriately excluded from bill synchronization. **Related Tasks** LATAM Task: 1367 ADHOC Task: 58906 Forward-Port-Of: odoo/enterprise#100549
This change updates URLs used for testing Wise direct deposit integrations to reflect Wise's upcoming domain change from sandbox.transferwise.tech to wise-sandbox.com. This ensures continued functionality of the sandbox environment and avoids disruptions to payment testing. Users may need to create a new sandbox account, but the impact is expected to be minimal.
Original PR description
Wise is deprecating their legacy sandbox (sandbox.transferwise.tech) in June 2026. Replace all sandbox URLs with the new wise-sandbox.com domain to avoid breaking test/sandbox payment flows. - API: api.sandbox.transferwise.tech → api.wise-sandbox.com - Portal: sandbox.transferwise.tech → wise-sandbox.com Note: API keys from the legacy sandbox are not transferable to the new environment. Affected users will need to create a new sandbox account, though the impact should be minimal as most customers do not actively use the sandbox. task-6074132 Forward-Port-Of: odoo/enterprise#112921
This update resolves an issue where the 'Edit Properties' button was unresponsive in the project dashboard. The fix ensures that this button only appears when relevant, streamlining the user experience for managing project database settings. This improves usability for users configuring their project KPIs.
Original PR description
Steps to produce: --- - Install `Databases` modules. - Go to project > Switch to list view and open project. - Click on the gear icon > Click `Edit Properties.` Observation: --- - Clicking `Edit…
Steps to produce: --- - Install `Databases` modules. - Go to project > Switch to list view and open project. - Click on the gear icon > Click `Edit Properties.` Observation: --- - Clicking `Edit Properties` does nothing. Root cause: --- - The `Edit Properties` action appears whenever a properties field is present in the view. - Currently, in `project.project` the field `database_kpi_properties` is added from database module (See [1]). - Here at [2], the field is added in `edit_project` view. - However, the field is only visible when `database_hosting` is set, and its value is different from `other`. Solution: --- - Patched `FormController.getStaticActionMenuItems()` and added a condition to make the `addPropertyFieldValue` menu item unavailable when the current model is `project.project`. [1]: https://github.com/odoo/enterprise/blob/84022deef3414096fcaf61f8d45c08393431e0ab/databases/models/project_project.py#L36 [2]: https://github.com/odoo/enterprise/blob/84022deef3414096fcaf61f8d45c08393431e0ab/databases/views/databases_project_views.xml#L158 Note: --- - Also found that, clicking `Edit Properties` from a page other than the KPI page does nothing. We could either show a guiding `dialog box` or limit the visibility of `Edit Properties` to the KPI page only. opw-5933007 --- Forward-Port-Of: odoo/enterprise#108056
This update fixes an issue where incorrect DTE (Digital Tax Document) XML files received by the system were automatically generating invoices. The fix reintroduces a check to discard these invalid DTEs, preventing the creation of unnecessary invoices and ensuring data accuracy. This improves the reliability of the purchase journal.
Original PR description
A supplier DTE xml should be discard when being fetched by a DTE incoming server if it has the wrong document type, meaning no account move should be created from it. Steps: - Have purchase journal using documents - Setup an incoming mail server, with DTE option enable, with email address X - Send an email to X with a supplier DTE xml of type 52 (TipoDTE element) - Fetch mails from the incoming server -> a bill has been generated and filled, it shouldn't Cause: The check on document type has been removed with the refactor 42744fcecdbd36ea0101070c68299227a9f204a6 Fix: Reintroduce the check in `_process_incoming_supplier_document` before creating any record opw-5978959 Forward-Port-Of: odoo/enterprise#112877
This pull request addresses inconsistencies in our language files by adding missing module references to the .weblate.json files. This ensures accurate translations are available for all Odoo Enterprise modules, improving the user experience for international customers. It's a routine maintenance task to maintain consistent localization.
Original PR description
Related: https://github.com/odoo/odoo/pull/254667 Forward-Port-Of: odoo/enterprise#113022 Forward-Port-Of: odoo/enterprise#111141
A thin line was appearing on the Bold 10 shape when used in website banners, depending on padding, size, and screen resolution. This fix adds an overlap adjustment to the shape to eliminate the unwanted visual glitch and ensure a clean appearance across different configurations.
Original PR description
Steps to reproduce: - Enter website edit mode - Insert `s_banner_connected` snippet - Add "Bold 10" shape (`19.svg`) - Depending on padding, size, resolution etc. a thin line appears This commit adds an overlap to fix the apparition of the line. | Before | After | |--------|--------| | <img width="1919" height="861" alt="image" src="https://github.com/user-attachments/assets/06ecf9c4-f9d8-44bd-b48f-a3d8f559d973" /> | <img width="1918" height="847" alt="image" src="https://github.com/user-attachments/assets/1bda5da4-53f4-4105-9af2-06a57da67d0a" /> | Forward-Port-Of: odoo/odoo#257616
5 changes
Resolved issues and error corrections
This update prevents the system from incorrectly syncing ‘e-Cobranza’ documents (collection notes) as vendor bills in the Uruguayan localization. This change aligns with how other related documents like ‘e-Remito’ and ‘e-Resguardos’ are handled, ensuring data consistency and accuracy.
Original PR description
This pull request improves the synchronization process of vendor bills within the Uruguayan localization (`l10n_uy_edi`). Currently, the system might fetch documents that are not technically bills during synchronization. With this change, the system will explicitly avoid synchronizing `e-Cobranza` (Collection notes or Receipts) documents as vendor bills. Reasoning: `e-Cobranza` documents function conceptually more like payment receipts rather than actual vendor bills. Pulling them into the system as bills creates inconsistencies. This update aligns the handling of `e-Cobranza` with the existing behavior for `e-Remito` (Delivery Guides) and `e-Resguardos` (Withholdings), which are also appropriately excluded from bill synchronization. **Related Tasks** LATAM Task: 1367 ADHOC Task: 58906 Forward-Port-Of: odoo/enterprise#100549
This change updates URLs used for testing Wise direct deposit integrations to reflect Wise's upcoming domain change. Replacing the old sandbox URLs prevents disruptions to testing and sandbox payment flows. Users may need to create a new sandbox account, but the impact is expected to be minimal.
Original PR description
Wise is deprecating their legacy sandbox (sandbox.transferwise.tech) in June 2026. Replace all sandbox URLs with the new wise-sandbox.com domain to avoid breaking test/sandbox payment flows. - API: api.sandbox.transferwise.tech → api.wise-sandbox.com - Portal: sandbox.transferwise.tech → wise-sandbox.com Note: API keys from the legacy sandbox are not transferable to the new environment. Affected users will need to create a new sandbox account, though the impact should be minimal as most customers do not actively use the sandbox. task-6074132 Forward-Port-Of: odoo/enterprise#112921
This update resolves an issue where the 'Edit Properties' button was unresponsive in the project settings. The fix ensures that this button is only displayed when relevant data is present, streamlining the user experience for managing database properties. This improves usability for users configuring their projects.
Original PR description
Steps to produce: --- - Install `Databases` modules. - Go to project > Switch to list view and open project. - Click on the gear icon > Click `Edit Properties.` Observation: --- - Clicking `Edit…
Steps to produce: --- - Install `Databases` modules. - Go to project > Switch to list view and open project. - Click on the gear icon > Click `Edit Properties.` Observation: --- - Clicking `Edit Properties` does nothing. Root cause: --- - The `Edit Properties` action appears whenever a properties field is present in the view. - Currently, in `project.project` the field `database_kpi_properties` is added from database module (See [1]). - Here at [2], the field is added in `edit_project` view. - However, the field is only visible when `database_hosting` is set, and its value is different from `other`. Solution: --- - Patched `FormController.getStaticActionMenuItems()` and added a condition to make the `addPropertyFieldValue` menu item unavailable when the current model is `project.project`. [1]: https://github.com/odoo/enterprise/blob/84022deef3414096fcaf61f8d45c08393431e0ab/databases/models/project_project.py#L36 [2]: https://github.com/odoo/enterprise/blob/84022deef3414096fcaf61f8d45c08393431e0ab/databases/views/databases_project_views.xml#L158 Note: --- - Also found that, clicking `Edit Properties` from a page other than the KPI page does nothing. We could either show a guiding `dialog box` or limit the visibility of `Edit Properties` to the KPI page only. opw-5933007 --- Forward-Port-Of: odoo/enterprise#108056
This update fixes an issue where incorrect DTE (Digital Tax Document) XML files received by the system were causing the creation of unnecessary invoices. The system now automatically discards these invalid DTEs, preventing incorrect data from being processed and ensuring accurate accounting. This improves data integrity and reduces potential errors.
Original PR description
A supplier DTE xml should be discard when being fetched by a DTE incoming server if it has the wrong document type, meaning no account move should be created from it. Steps: - Have purchase journal using documents - Setup an incoming mail server, with DTE option enable, with email address X - Send an email to X with a supplier DTE xml of type 52 (TipoDTE element) - Fetch mails from the incoming server -> a bill has been generated and filled, it shouldn't Cause: The check on document type has been removed with the refactor 42744fcecdbd36ea0101070c68299227a9f204a6 Fix: Reintroduce the check in `_process_incoming_supplier_document` before creating any record opw-5978959 Forward-Port-Of: odoo/enterprise#112877
A thin line was appearing on the Bold 10 shape when used in website banners, depending on padding, size, and screen resolution. This fix adds an overlap adjustment to the shape to eliminate the unwanted line and improve the visual appearance of websites using this design element.
Original PR description
Steps to reproduce: - Enter website edit mode - Insert `s_banner_connected` snippet - Add "Bold 10" shape (`19.svg`) - Depending on padding, size, resolution etc. a thin line appears This commit adds an overlap to fix the apparition of the line. | Before | After | |--------|--------| | <img width="1919" height="861" alt="image" src="https://github.com/user-attachments/assets/06ecf9c4-f9d8-44bd-b48f-a3d8f559d973" /> | <img width="1918" height="847" alt="image" src="https://github.com/user-attachments/assets/1bda5da4-53f4-4105-9af2-06a57da67d0a" /> | Forward-Port-Of: odoo/odoo#257616
1 change
Resolved issues and error corrections
This update fixes an issue on mobile devices where the buttons within the transfer chatter view were too small, causing text to overflow and making the interface difficult to use. The change ensures that buttons are properly sized and display all text clearly, improving the user experience on mobile.
Original PR description
Partial backport of d16480179ed73f25e0465e42c6fdef64e4fdc502 Steps to reproduce ================== - Navigate to Barcode, click on any transfer - Click on the name of the transfer in the header to open the form view - Scroll down to the chatter, the buttons are too small to contain the text, and much of the text flows over to other UI elements Cause of the issue ================== The barcode style override every buttons including the ones inside the chatter opw-6082959 Forward-Port-Of: odoo/enterprise#112581
1 change
Resolved issues and error corrections
This update fixes an issue on mobile devices where the buttons within the transfer chatter view were too small, causing text to overflow and making the interface difficult to use. The change ensures that buttons are properly sized and displayed, improving the user experience when viewing transfers on smartphones and tablets.
Original PR description
Partial backport of d16480179ed73f25e0465e42c6fdef64e4fdc502 Steps to reproduce ================== - Navigate to Barcode, click on any transfer - Click on the name of the transfer in the header to open the form view - Scroll down to the chatter, the buttons are too small to contain the text, and much of the text flows over to other UI elements Cause of the issue ================== The barcode style override every buttons including the ones inside the chatter opw-6082959 Forward-Port-Of: odoo/enterprise#112581
2 changes
Resolved issues and error corrections
This update fixes an issue where users were incorrectly prompted for passwords when downloading encrypted documents that didn't actually require them. The change now correctly checks if a password is needed before attempting a download, ensuring a smoother and more reliable experience for users. This resolves a previous blocking issue.
Original PR description
Related ticket: https://www.odoo.com/odoo/project/49/tasks/5400441 Previously, if a user went to download a document, we would check if it was encrypted. If so, we would redirect to ask for a password. But the problem with that is, not all encrypted documents require passwords. In that case, we would ask for a password when none existed, thus blocking the user from downloading the document. Now we check if a password is required to access the document instead of whether the document is encrypted. That way, we won't redirect to ask for a password when there is no password. Docs about PdfFileReader's `decrypt` method, before and after a major change: https://pypdf2.readthedocs.io/en/2.3.0/modules/PdfReader.html https://pypdf2.readthedocs.io/en/2.12.0/modules/PdfReader.html Forward-Port-Of: odoo/enterprise#102602
This update fixes an issue on mobile devices where the buttons within the transfer chatter view were too small, causing text to overflow and making the interface difficult to use. The change ensures that buttons are appropriately sized for mobile screens, improving the user experience when managing transfers.
Original PR description
Partial backport of d16480179ed73f25e0465e42c6fdef64e4fdc502 Steps to reproduce ================== - Navigate to Barcode, click on any transfer - Click on the name of the transfer in the header to open the form view - Scroll down to the chatter, the buttons are too small to contain the text, and much of the text flows over to other UI elements Cause of the issue ================== The barcode style override every buttons including the ones inside the chatter opw-6082959 Forward-Port-Of: odoo/enterprise#112581
5 changes
Resolved issues and error corrections
This update resolves a bug in the account reports testing environment. The fix addresses inconsistencies in data handling and ensures report lines correctly display invoice references. This improves the reliability of test results and the accuracy of account reporting.
Original PR description
Now that context is not hacked, some flush and write are done a bit differently. Fix tests. account_reports: probably due to a missing flush or data computation tests were a bit hacked to account for invalid data. This is now fixed, report line correctly contains the invoice reference.
This update prevents the system from incorrectly syncing ‘e-Cobranza’ documents (collection notes) as vendor bills in the Uruguayan localization. This change aligns with how we handle other related documents like ‘e-Remito’ and ‘e-Resguardos’, ensuring data consistency and accuracy for vendor billing.
Original PR description
This pull request improves the synchronization process of vendor bills within the Uruguayan localization (`l10n_uy_edi`). Currently, the system might fetch documents that are not technically bills during synchronization. With this change, the system will explicitly avoid synchronizing `e-Cobranza` (Collection notes or Receipts) documents as vendor bills. Reasoning: `e-Cobranza` documents function conceptually more like payment receipts rather than actual vendor bills. Pulling them into the system as bills creates inconsistencies. This update aligns the handling of `e-Cobranza` with the existing behavior for `e-Remito` (Delivery Guides) and `e-Resguardos` (Withholdings), which are also appropriately excluded from bill synchronization. **Related Tasks** LATAM Task: 1367 ADHOC Task: 58906 Forward-Port-Of: odoo/enterprise#100549
This update resolves an issue where the 'Edit Properties' button was unexpectedly appearing in the project dashboard. The fix prevents the button from showing up when it's not relevant, streamlining the user experience for project management. This ensures users only see options that apply to their current project setup.
Original PR description
Steps to produce: --- - Install `Databases` modules. - Go to project > Switch to list view and open project. - Click on the gear icon > Click `Edit Properties.` Observation: --- - Clicking `Edit…
Steps to produce: --- - Install `Databases` modules. - Go to project > Switch to list view and open project. - Click on the gear icon > Click `Edit Properties.` Observation: --- - Clicking `Edit Properties` does nothing. Root cause: --- - The `Edit Properties` action appears whenever a properties field is present in the view. - Currently, in `project.project` the field `database_kpi_properties` is added from database module (See [1]). - Here at [2], the field is added in `edit_project` view. - However, the field is only visible when `database_hosting` is set, and its value is different from `other`. Solution: --- - Patched `FormController.getStaticActionMenuItems()` and added a condition to make the `addPropertyFieldValue` menu item unavailable when the current model is `project.project`. [1]: https://github.com/odoo/enterprise/blob/84022deef3414096fcaf61f8d45c08393431e0ab/databases/models/project_project.py#L36 [2]: https://github.com/odoo/enterprise/blob/84022deef3414096fcaf61f8d45c08393431e0ab/databases/views/databases_project_views.xml#L158 Note: --- - Also found that, clicking `Edit Properties` from a page other than the KPI page does nothing. We could either show a guiding `dialog box` or limit the visibility of `Edit Properties` to the KPI page only. opw-5933007 --- Forward-Port-Of: odoo/enterprise#108056
This update fixes an error preventing Intervat from properly verifying our connections. The issue stemmed from outdated JWK keys being archived on IAP, which caused authentication failures. The fix involves ensuring Intervat can access the most current JWK keys, restoring seamless communication with Intervat.
Original PR description
When we open a connection in intervat, we initialize a JWK on IAP side,
then we use the private key linked with this JWK to sign our requests.
The problem is on IAP, we have a cron who archive JWK older than a week.
As the archived JWK are hidden in our JWKS endpoint, Intervat is no
longer capable of verifying our signatures, leading to this error:
`{"error_description":"JWT is not valid" "error":"invalid_client"}`.
To fix this, we might need to call IAP first to unarchive the JWK first.
no-task
Forward-Port-Of: odoo/enterprise#112719This update addresses an issue where incorrect DTE (Digital Tax Document) XML files were causing the system to generate invoices even when they were invalid. The fix reintroduces a check to discard these files, preventing the creation of unnecessary invoices and ensuring data accuracy. This improves the reliability of the purchase order process.
Original PR description
A supplier DTE xml should be discard when being fetched by a DTE incoming server if it has the wrong document type, meaning no account move should be created from it. Steps: - Have purchase journal using documents - Setup an incoming mail server, with DTE option enable, with email address X - Send an email to X with a supplier DTE xml of type 52 (TipoDTE element) - Fetch mails from the incoming server -> a bill has been generated and filled, it shouldn't Cause: The check on document type has been removed with the refactor 42744fcecdbd36ea0101070c68299227a9f204a6 Fix: Reintroduce the check in `_process_incoming_supplier_document` before creating any record opw-5978959 Forward-Port-Of: odoo/enterprise#112877
4 changes
Resolved issues and error corrections
This update prevents the system from incorrectly syncing ‘e-Cobranza’ documents (collection notes) as vendor bills in the Uruguayan localization. This change aligns with how other documents like ‘e-Remito’ and ‘e-Resguardos’ are handled, ensuring data consistency and accuracy for vendor billing.
Original PR description
This pull request improves the synchronization process of vendor bills within the Uruguayan localization (`l10n_uy_edi`). Currently, the system might fetch documents that are not technically bills during synchronization. With this change, the system will explicitly avoid synchronizing `e-Cobranza` (Collection notes or Receipts) documents as vendor bills. Reasoning: `e-Cobranza` documents function conceptually more like payment receipts rather than actual vendor bills. Pulling them into the system as bills creates inconsistencies. This update aligns the handling of `e-Cobranza` with the existing behavior for `e-Remito` (Delivery Guides) and `e-Resguardos` (Withholdings), which are also appropriately excluded from bill synchronization. **Related Tasks** LATAM Task: 1367 ADHOC Task: 58906 Forward-Port-Of: odoo/enterprise#100549
This update fixes an issue on mobile devices where the buttons within the transfer chatter view were too small, causing text to overflow and making the interface difficult to use. The change ensures that buttons are properly sized and display all text clearly, improving the user experience on mobile. This resolves a reported usability problem.
Original PR description
Partial backport of d16480179ed73f25e0465e42c6fdef64e4fdc502 Steps to reproduce ================== - Navigate to Barcode, click on any transfer - Click on the name of the transfer in the header to open the form view - Scroll down to the chatter, the buttons are too small to contain the text, and much of the text flows over to other UI elements Cause of the issue ================== The barcode style override every buttons including the ones inside the chatter opw-6082959 Forward-Port-Of: odoo/enterprise#112581
This update fixes an issue where incorrect DTE (Digital Tax Document) XML files received by the system were automatically generating invoices. The fix reintroduces a check to discard these invalid DTEs, preventing the creation of unnecessary invoices and ensuring data accuracy. This improves the reliability of the purchase journal.
Original PR description
A supplier DTE xml should be discard when being fetched by a DTE incoming server if it has the wrong document type, meaning no account move should be created from it. Steps: - Have purchase journal using documents - Setup an incoming mail server, with DTE option enable, with email address X - Send an email to X with a supplier DTE xml of type 52 (TipoDTE element) - Fetch mails from the incoming server -> a bill has been generated and filled, it shouldn't Cause: The check on document type has been removed with the refactor 42744fcecdbd36ea0101070c68299227a9f204a6 Fix: Reintroduce the check in `_process_incoming_supplier_document` before creating any record opw-5978959 Forward-Port-Of: odoo/enterprise#112877
This update reorganizes test code to ensure tests are located in the same module where the test models they use are defined. A test was moved from the base module to the test_testing_utilities module where the res.config.test model is actually defined. This improves code organization and maintainability without affecting any user-facing functionality.
Original PR description
Move the test to test_testing_utilities where the model res.config.test is defined. Move test introduced in odoo/odoo#257033. runbot-242309 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#257514