Daily updates from Odoo
Navigate
Branch
Sunday, December 28, 2025
8 changes
3 changes
Resolved issues and error corrections
This update fixes a potential issue where sales orders linked to partners without addresses could be paid through the Point of Sale (PoS) system. Previously, this resulted in errors preventing session closure. This change ensures compliance with Fiskaly regulations and prevents payment failures.
Original PR description
### Description According to Fiskaly regulations, partners linked to PoS orders must have an address (street and zip code). A previous [commit] (https://github.com/odoo/enterprise/commit/af3a59ee8492693e20807ae30dc58038229f96cb) prevented adding such a client on a normal flow. However, before this commit it was still possible to pay a sale order linked to such a contact through PoS and this will raise a bad request error when closing the session and will prevent closing it. ### How to reproduce: * Setup a Fiskaly PoS config and open it. * Create a normal sale order linked to a partner with no address. * Select the sale order from pos and pay it. * Close the session opw-5228944 Forward-Port-Of: odoo/odoo#235331
This update fixes a potential issue where sales orders linked to partners without addresses could be paid through the Point of Sale (PoS) system. Previously, this would cause payment errors and prevent session closure. This change ensures compliance with Fiskaly regulations by requiring a valid address for PoS orders, improving data accuracy and preventing payment disruptions.
Original PR description
### Description According to Fiskaly regulations, partners linked to PoS orders must have an address (street and zip code). A previous [commit] (https://github.com/odoo/enterprise/commit/af3a59ee8492693e20807ae30dc58038229f96cb) prevented adding such a client on a normal flow. However, before this commit it was still possible to pay a sale order linked to such a contact through PoS and this will raise a bad request error when closing the session and will prevent closing it. ### How to reproduce: * Setup a Fiskaly PoS config and open it. * Create a normal sale order linked to a partner with no address. * Select the sale order from pos and pay it. * Close the session Community PR: https://github.com/odoo/odoo/pull/235331 opw-5228944 Forward-Port-Of: odoo/enterprise#99286
This update fixes a vulnerability in the Point of Sale testing process. Previously, tests relied on translated button labels, making them susceptible to issues when translations changed. The fix ensures tests use the default language, improving stability and reducing the risk of test failures.
Original PR description
In the tour added in this commit[^1], they switched the language to French to test `,` as a decimal separator. The test depends on a button label to click that was translated to French. This is pretty brittle since translations can change, and also not necessary for what we need to test. We just change the decimal separator on the current language in the test so the label can keep the source language. This is also done in other places in the tours. (Issue found when translating saas-19.1) [^1]: https://github.com/odoo/odoo/commit/c712835cf7fc364a50ad9797f933df148720e829 Forward-Port-Of: odoo/odoo#241485
3 changes
New functionality added to Odoo
This update enhances the testing process for the POS Restaurant module's preparation display functionality. By adding comprehensive HOOT tests and a dedicated test environment, the team ensures the display works correctly and reliably, contributing to a more stable and user-friendly experience for restaurant operators.
Original PR description
In this commit: --- - Added HOOT test coverage for the POS Restaurant module's preparation display. - Introduced `setupPosPrepDisplayEnv` to mock and initialize the preparation display test environment. - Added test coverage for core components, models, and service logic. - Adjust hoot case for pos_urban_piper. task-5225193 Related PR: - https://github.com/odoo/odoo/pull/234474 Forward-Port-Of: odoo/enterprise#98849
Enhancements to existing features
This update enhances the synchronization of product data within the Point of Sale module. Specifically, it now uses unique record identifiers (UUIDs) for more accurate matching and improves test data setup by adding category information. This ensures data consistency and reliability for Point of Sale operations.
Original PR description
In this commit: --- - Improved `sync_from_ui` function to support record UUID-based relational mapping. - Added `pos_categ_ids` field in product data for better category linkage in tests. task-5225193 Related PR: - https://github.com/odoo/enterprise/pull/98849 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#234474
Resolved issues and error corrections
This update fixes a vulnerability in the Point of Sale testing process. Previously, tests relied on translated button labels, making them susceptible to issues when translations changed. The fix ensures tests use the default language's decimal separator, improving test stability and reducing the risk of failures.
Original PR description
In the tour added in this commit[^1], they switched the language to French to test `,` as a decimal separator. The test depends on a button label to click that was translated to French. This is pretty brittle since translations can change, and also not necessary for what we need to test. We just change the decimal separator on the current language in the test so the label can keep the source language. This is also done in other places in the tours. (Issue found when translating saas-19.1) [^1]: https://github.com/odoo/odoo/commit/c712835cf7fc364a50ad9797f933df148720e829 Forward-Port-Of: odoo/odoo#241485
2 changes
Resolved issues and error corrections
This update fixes a technical issue where unused sign item roles were accumulating in the database, causing performance problems. A simple workaround – creating a dummy sign item – has been implemented to trigger database cleanup, ensuring data remains organized and efficient. This improves the overall stability of the sign management feature.
Original PR description
Fixes an issue where sign item roles were created but never deleted if they had no sign items linked to them. These orphaned roles were no longer shown in the app and remained in the database indefinitely. To address this, a dummy sign item is now created for each new sign item role. This allows the autovacuum logic to detect and automatically clean up unused roles and dummy items. Without this dummy item, it would be impossible to determine if a role is truly orphaned. task-4971485 Forward-Port-Of: odoo/enterprise#102957 Forward-Port-Of: odoo/enterprise#91189
This update fixes a potential issue where sales orders linked to partners without addresses could be paid through the Point of Sale (PoS) system. Previously, this would cause a payment error when closing the session, preventing transactions. This change ensures compliance with Fiskaly regulations by requiring a valid address for all PoS-related sales orders.
Original PR description
### Description According to Fiskaly regulations, partners linked to PoS orders must have an address (street and zip code). A previous [commit] (https://github.com/odoo/enterprise/commit/af3a59ee8492693e20807ae30dc58038229f96cb) prevented adding such a client on a normal flow. However, before this commit it was still possible to pay a sale order linked to such a contact through PoS and this will raise a bad request error when closing the session and will prevent closing it. ### How to reproduce: * Setup a Fiskaly PoS config and open it. * Create a normal sale order linked to a partner with no address. * Select the sale order from pos and pay it. * Close the session Community PR: https://github.com/odoo/odoo/pull/235331 opw-5228944 Forward-Port-Of: odoo/enterprise#99286