Saturday, November 15, 2025
3 changes · master
Resolved issues and error corrections
This fix prevents the browser from reusing an outdated saved copy when a spreadsheet tab is duplicated. Users should now see the latest spreadsheet changes in duplicated tabs, reducing confusion and potential work errors.
Original PR description
It happens that browser may use a cache if there's no explicit cache control/expiration time: https://httpwg.org/specs/rfc9111.html#heuristic.freshness Steps to reproduce (non-deterministic): - create a new spreadsheet - do some changes, edit a few cells - right click on the tab and hit "Duplicate" => the spreadsheet is not up-to-date on the duplicated tab. The browser loaded the response from "disk cache" instead of fetching the latest data from the server. I'm using Chrom Version 142.0.7444.162 (Official Build) (64-bit) We add an explicit cache control. Forward-Port-Of: odoo/enterprise#99426
Fixed an error that could occur when adding a user to a new database project before any databases were linked. The user management wizard now handles this empty state correctly, preventing an unexpected crash and allowing the workflow to continue.
Original PR description
Versions -------- - 19.0+ Steps ----- 1. Go to Databases; 2. open a new project; 3. enter any name, hosting provider & URL; 4. under User Management, click on "Add a user". Issue ----- Traceback: > `ValueError: Compute method failed to assign databases.manage_users.wizard(<NewId 0x71e8c0d8fd80>,).everywhere_user_ids` Cause ----- The `_compute_everywhere_user_ids` method computes the value of a non-stored field. Consequently, every record in `self` needs have some value assigned to `everywhere_user_ids` during the compute, but currently, if the `database_ids` field is empty, `continue` is used without assigning a value. Solution -------- If the record doesn't have any known `database_ids`, set `everywhere_user_ids` to `None`. opw-5170587 Forward-Port-Of: odoo/enterprise#99200
The NACHA payment file now formats the company identification field according to official ACH rules. This helps payroll and payment files be accepted consistently by banks by using the correct spacing instead of zero-padding for this alphanumeric value.
Original PR description
According to https://achdevguide.nacha.org/ach-file-overview: - An alphanumeric field must be left-justified and post-padded with spaces. - A numeric field must be unsigned, right-justified and pre-padded with zeros. The Company Identification being an alphanumeric value (see https://achdevguide.nacha.org/ach-file-details), it should be left-justified and post-padded with spaces even in the type 8 record, like it is actually in the type 5 record. opw-5048564 Forward-Port-Of: odoo/enterprise#99469 Forward-Port-Of: odoo/enterprise#98922