Daily updates from Odoo
Tuesday, September 2, 2025
4 changes · 18.0
Enhancements to existing features
Website module upgrades now process large page data in smaller batches instead of loading everything at once. This reduces memory usage and helps prevent upgrade failures that could block access to a database.
Original PR description
### Issue A user cannot access their database (Bad Gateway) after trying to upgrade a module. ### Analysis The root cause is the out of memory error, stemming from the SQL query fetching all `arch_db` and then fetching them with `fetchall`. ### Solution This commit optimizes the loading of module terms in the `ir_module_module` model by iterating over the rows per chunks. This change reduces the memory footprint, which is crucial when dealing with heavy `arch_db` in the `ir_ui_view` table. We also filter out `if not generic_arch_db` directly in the SQL query instead of on the Python side. After applying this patch, there is no more `MemoryError` and the user can access their database. ### References opw-5014922 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#223439
Temporary timeout issues when submitting Indian e-invoices through MasterGST are now treated as warnings instead of blocking errors. This prevents invoices from getting stuck and lets scheduled background jobs retry them automatically.
Original PR description
Before this commit: --- while requesting for E-invoice on MasterGST, If there was a ConnectionTimeout on the IAP server the response was treated as an error. This caused invoices to enter an error state and prevented them from being retried by cron. In this commit: --- Timeout errors are treated as warnings by setting blocking_level to "warning" for "timeout" error codes. This allows cron jobs to automatically retry such invoices. task-4970444 Forward-Port-Of: odoo/odoo#221185
UAE payroll now better supports payslips for employees whose contracts are based on attendance or planning schedules. This helps ensure salary calculations match actual working arrangements and includes added test coverage for these scenarios.
Original PR description
Updates for the salary rules to accomodate Attendance and Planning-based contracts and test cases for said scenarios opw-[4873312](https://www.odoo.com/odoo/all-tasks/4873312)
Accounting reports grouped by account code now also show the matching account name for the current company. This makes consolidated multi-company reporting easier to read when several accounts are mapped to the same code.
Original PR description
In the current consolidation, you can make multi-company accounts and assign a code for each company. But a code must be unique inside each company. So it is not designed to map multiple accounts from a second company into one account of a first company. It is actually possible to achieve that effect by not making the accounts of the second company belong to the first company, and still make the code mapping. So you can make several accounts from the second company, map to the same code for the first company. Thus grouping by account codes become interesting for the accounting reports, in order to get a view of that consolidation. In order to make this reporting more clear, the name of the account corresponding to the account code (in the current company) is now shown when grouping by account code. task-4801891