Thursday, April 24, 2025
9 changes · 17.0
Resolved issues and error corrections
The document layout setup no longer crashes when a company uses an unusually tall, narrow logo. This helps users configure company documents reliably without needing to resize or replace valid logo images first.
Original PR description
This error occurs when a user attempts to `Configure Document Layout` in settings using a large vertically-oriented image. Steps to Reproduce: - Install the `web` module. - Go to `Settings`. - In the…
This error occurs when a user attempts to `Configure Document Layout` in settings using a large vertically-oriented image. Steps to Reproduce: - Install the `web` module. - Go to `Settings`. - In the `companies` section, under Your Company, click on `Update Info`. - Upload an image with dimensions width = 8 and height = 901. - Go back, and in the Companies section, click `Configure Document Layout`. ValueError: height and width must be > 0 This error is due to the current logic in `base_document_layout.py`, where the width (w) is computed using int(50 * base_w / base_h). For highly vertical images (e.g., width = 8, height = 901), this calculation results in w = 0, which subsequently causes a ValueError when passed to the resize() function. This commit resolves the error by using `math.ceil` to compute the width (w) instead of int, ensuring that the value is never zero, even for extremely vertical images. Sentry-6516888945 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix adds missing identifiers for Buckaroo payment methods so they can be recognized correctly during payment processing. It helps reduce setup or transaction issues for businesses using Buckaroo as a payment provider.
Original PR description
Add missing codes for payment methods --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures website robots.txt settings are applied correctly when a site is accessed through an internationalized domain name, whether entered in encoded or readable form. This helps businesses using non-English characters in their domain names keep search engine crawling rules consistent and accurate.
Original PR description
When the website domain is defined using punycode (e.g., `xn--ingenieurbro-mlb.localhost`), navigating to the Unicode URL (e.g., `Ingenieurbüro.localhost`) would not reflect the updated `robots.txt`. Steps to reproduce the issue: - Navigate to Website > Configuration > Website. - Set a domain name with punycode (e.g., http://xn--ingenieurbro-mlb.localhost:8069). - Go to settings and modify the robots.txt file. - Visit http://Ingenieurbüro.localhost:8069 and notice that the changes are not reflected. This commit ensures the correct handling of punycode domains so that the robots.txt is properly served, regardless of whether the domain is accessed in Unicode or punycode form. opw-4641081
Kitchen preparation tickets now clearly show which items belong to a combo order. This prevents restaurant staff from mistaking combo components for separate standalone items, helping reduce preparation errors.
Original PR description
When sending a combo to a preparation printer, the combo items where not indented correctly. This was leading to a preparation ticket that made it look like all items were normal items, instead of being part of a combo. Steps to reproduce: ------------------- * Create a combo product A * Setup a kitchen printer in the PoS * Open PoS and add the combo product A * Send the order to the kitchen printer > Observation: The preparation ticket does not show the combo items > indented correctly Why the fix: ------------ We add a new fields in the `changes` that state if the line is part of a combo. If it is part of a combo, we add a css class that will indent the line accordingly. opw-4459211
This fixes an issue where Romanian VAT validation compared the first tax number twice instead of checking the second one. It helps prevent incorrect VAT validation results for Romanian business partners.
Original PR description
During this commit: https://github.com/odoo/odoo/commit/2f86fb973a426a4d6c10d41d61dc524955aebb6b we checked the tin1 twice instead of checking the second one task: 4743115 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale customer search now finds contacts even when a phone number is typed without spaces but saved with spaces. This makes customer lookup faster and more reliable at checkout, reducing missed matches for cashiers.
Original PR description
Before this commit, searching for a customer in the PoS using a phone number without spaces (e.g. "0612345678") would return no results if the number was stored with spaces (e.g. "06 12 34 56 78"). opw-4683209 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents duplicate future public holiday leave records from being created when an employee is unarchived even though they are already active. It avoids incorrect time-off balances and cleanup work after contract signing workflows update employee records.
Original PR description
To reproduce: - Install both `hr_contract_salary` and `project_timesheet_holidays` - Create a public holiday for the company (ex. on May 01) - Create a employee => This create leaves for employee's company public holidays - Create a contract for that employee - Send a signing request to both employee and HR responsible - The employee sign the document - The responsible sign the document => At that time, we're going to update the contract after both parties signed the contract and force unarchiving the employee even if it's already active. This commit ensure that unarchiving an already active employee does not create duplicate *future* public holidays. opw-4134712 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The GST reporting process now checks whether a company has a valid GST token before running scheduled GST API calls. This prevents failed or unnecessary background processing and keeps GST reporting automation aligned with the existing manual validation flow.
Original PR description
This PR adds a validation check for a company's GST token before making GST API calls via cron. These validations already exist when making GST API calls through the GST return period but were missing in the cron execution. This ensures that no unnecessary cron execution and api call takes place. task-4350780
Mexican electronic invoice files will no longer include an unused trade-related namespace in the generated XML. This keeps the document output cleaner and avoids confusion when reviewing or validating invoice files, without changing invoice behavior.
Original PR description
With this commit we remove the namespaces that are not used in the cdfi document. Steps: - Create an invoice and send the edi document - Look at the xml -> namespace `xmlns:cce20="http://www.sat.gob.mx/ComercioExterior20"` is included but unused opw-4493568