Saturday, September 12, 2026
5 changes · 19.0
Resolved issues and error corrections
The Chilean electronic invoicing workflow now handles cases where the tax authority returns an empty status response. This prevents scheduled invoice status checks from crashing and helps keep document processing running smoothly.
Original PR description
When checking the status of a DTE, sometimes the response will have no `text`. This causes a traceback error that halts execution of the cron `cron_run_sii_workflow`. opw-6322106 Forward-Port-Of: odoo/enterprise#130873 Forward-Port-Of: odoo/enterprise#129582
This change prevents some Odoo pages from incorrectly showing a 404 error when the server runs on Windows. It keeps web address handling consistent across operating systems, improving reliability for Windows deployments.
Original PR description
* URL paths are POSIX (forward slashes). Use posixpath so the `..` jail still applies while keeping `/` separators — os.path.normcase / normpath rewrite `/`->`\` on Windows and break the split below. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where invoicing a previous point-of-sale order could send the wrong cancellation information to Spain's AEAT tax system. The correction ensures the original simplified receipt is cancelled instead of the newly created full invoice, helping avoid inaccurate tax reporting.
Original PR description
When creating an invoice for a previous POS order, the data sent to AEAT cancels the full invoice instead of the order's simplified invoice. Steps to reproduce: - Open a POS and make a sale without invoicing it; - In the POS, go to the Order tab; - Select the order and fully invoice it. Issue: The AEAT cancellation line added to the pos order actually cancels the full invoice just created [opw-6471927](https://www.odoo.com/odoo/project/49/tasks/6471927) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue where company card payments could be blocked if a previous expense created by the same card had its date removed. Expenses without a date are now only counted in all-time limits, allowing future card transactions to continue normally.
Original PR description
Fix a traceback preventing card users to make any payment with their card if at least one expense created by said card has no date Steps to reproduce: - Install hr_expense_stripe_demo (to access the test wizards) - Setup the stripe (demo) account with a valid card and funds - Create one transaction with the card - Remove the date of the generated expense -> Any further transaction with that card will fail After this commit: An expense with no date is considered only in the 'all time' Ticket [link](https://www.odoo.com/odoo/project.task/6326124) opw-6326124
Manufacturing order overviews now calculate totals correctly even when related work orders do not have an employee assigned. This prevents misleading cost summaries and helps managers rely on accurate production cost information.
Original PR description
Description of the issue/feature this PR addresses: Resolves an issue where Manufacturing Order (MO) summary calculations produced incorrect totals when associated Work Orders had no assigned employee. Current behavior before PR: <img width="2419" height="802" alt="mo-wo-employee-fix-before" src="https://github.com/user-attachments/assets/9a0d64b4-2ca3-4732-9ac7-39673e0ae319" /> Short-circuiting the logic when a work order has no associated employee causes an error in the overview's cost calculation. Behavior after PR: <img width="2389" height="641" alt="mo-wo-employee-fix-after" src="https://github.com/user-attachments/assets/f2b67e84-c149-4d05-be30-f834e62e0882" /> By updating it to no longer short-circuit it now correctly calculates the cost of the manufacturing order. opw-6464637 Forward-Port-Of: odoo/enterprise#130554 Forward-Port-Of: odoo/enterprise#128465