Daily updates from Odoo
Saturday, November 29, 2025
6 changes
1 change
Resolved issues and error corrections
This update resolves a previous issue where the course publisher editor wouldn't consistently load correctly. By ensuring the iframe is loaded first, the system now provides a more reliable and predictable experience for users accessing course content. This enhances the overall user experience and reduces potential disruptions.
Original PR description
In this commit, we fix a non deterministic behavior by ensuring the iframe is loaded before it try to open editor. runbot-232846
1 change
Resolved issues and error corrections
This pull request addresses minor inconsistencies in address data processing for Odoo's e-commerce modules, specifically focusing on Brazil (l10n_br_avatax) and Colombia (l10n_co_edi). The changes ensure accurate city-to-country ID mapping, resolving potential issues with checkout processes and tax calculations within these regions. This improves the reliability of the e-commerce experience for customers in these countries.
2 changes
Resolved issues and error corrections
A test case in the Enterprise accounting module was failing due to differences in payment state handling between the community and enterprise versions. This change moves the test case to the Enterprise module to ensure it accurately reflects the expected behavior, resolving the reported error.
Original PR description
Community build was failing with: ``` test_bill_state_change_on_payment_state self.assertEqual(payment.invoice_ids.payment_state, 'not_paid') AssertionError: 'paid' != 'not_paid' - paid + not_paid ``` [Commit](https://github.com/odoo/odoo/pull/234725/commits/5dc43a2156e5b176e3236583b45b4838a987ee7d) In community there is no any `in_payment` state for account move records. As on changing payment state to draft It stayed in the `paid` only. `in_payment` state introduced in the enterprise module. So the test case is failing for the community version. To fix this I've moved the test case to the enterprise to retain the expected behaviour. runbot error: 234453 Forward-Port-Of: odoo/enterprise#100865 Forward-Port-Of: odoo/enterprise#100834
A test case in the community version of Odoo's account module was failing due to a difference in payment state handling between the community and enterprise versions. This update moved the test case to the enterprise environment to ensure it accurately reflects the expected behavior, resolving the reported error.
Original PR description
Community build was failing with: ``` test_bill_state_change_on_payment_state self.assertEqual(payment.invoice_ids.payment_state, 'not_paid') AssertionError: 'paid' != 'not_paid' - paid + not_paid ``` [Commit](https://github.com/odoo/odoo/pull/234725/commits/5dc43a2156e5b176e3236583b45b4838a987ee7d) In community there is no any `in_payment` state for account move records. As on changing payment state to draft It stayed in the `paid` only. `in_payment` state introduced in the enterprise module. So the test case is failing for the community version. To fix this I've moved the test case to the enterprise to retain the expected behaviour. runbot error: 234453 Forward-Port-Of: odoo/odoo#237933 Forward-Port-Of: odoo/odoo#237881
2 changes
Resolved issues and error corrections
This update removes an outdated and confusing reference to a previous module name ('finkok') within the Mexican VAT (l10n_mx_edi) integration. The change simplifies the codebase and reduces potential confusion for developers. This is a routine maintenance fix.
Original PR description
It has been some time since finkok changed its name to quadrum, and now no one remembers quadrum as finkok. Having it in the name only causes more confusion, so we decided to simply remove it. I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#100663
This update fixes a technical issue that prevented the system from merging certain PDF files, specifically Bills, due to errors in the PDF processing library. The change adds a user-friendly error message instead of a technical traceback, ensuring a smoother experience for users when encountering malformed PDFs. This resolves a potential disruption in generating reports.
Original PR description
Currently some PDFs cause error in PyPDF (Version 1 and 2) and cannot be merged. Steps to reproduce: - Create 2+ Bills with specific PDF (example found in ticket) - From Bills list view, select both and click Download > Original bills Issue: Traceback will raise `PyPDF2.errors.PdfReadError: Can't read object stream: Stream has ended unexpectedly` Thsi occurs because the version of PyPDF currently in use (2.12.1) cannot recover when working an odd PDF file having wrong length markers. This commit will add a nice error explaining to user what's going on. opw-5142961 Forward-Port-Of: odoo/odoo#234587