Tuesday, May 19, 2026
5 changes · 17.0
Resolved issues and error corrections
This update fixes an issue where check amounts were not being properly rounded in the Philippines (PH) version of Odoo. Previously, the check amount in words displayed an incorrect decimal format with 'ONLY' appended. This change ensures accurate check formatting for PH transactions, improving financial reporting and compliance.
Original PR description
Current behaviour: --- When paying with checks, the amount is not rounded in the check amount in words string. Steps to reproduce: --- 1. Switch to PH company 2. Set setting Check Layout as "Print Check - PH" 3. Create a new vendor bill 4. Add a product with a specific price like 91490.15 5. Confirm the bill, click on Register Payment 6. Select Payment Method "Checks", Create Payment 7. Go to the payment, Amount in Words is wrong 8. Ninety-One Thousand Four Hundred Ninety And 15000000001/100 ONLY Expected behaviour: --- The decimal amount should be rounded, and "ONLY" shouldn't appear. Fix: --- Rounded the pay amount And backported: https://github.com/odoo/enterprise/commit/bb6c9848665709c14c5113b2c98976f869cd473b opw-6058344
This update resolves a bug that prevented users from accessing the community forum when multiple forums were configured within the helpdesk. The fix corrects an error in how the forum templates were rendered, ensuring consistent functionality across different forum setups. This ensures all users can access the community forum.
Original PR description
*=website_helpdesk_slides_forum,website_helpdesk_forum Currently an exception is generated when the user tries to open the community forum of the helpdesk by following steps. - Install `Website…
*=website_helpdesk_slides_forum,website_helpdesk_forum Currently an exception is generated when the user tries to open the community forum of the helpdesk by following steps. - Install `Website Slides Forum Helpdesk (website_helpdesk_slides_forum)` - Go to `Helpdesk` > `Configuration` > `Helpdesk team` > `Customer care` - Set more than one forums inside `Community Forum` and save - Go to the website and open `Help` page - Error will generate when clicking `Ask the community` First Error: `QWebError: Error while rendering the template: KeyError: '_forums'` Second error when we try above step by only installing `website_helpdesk_forum`: `ValueError: View 'website_helpdesk_forum.forum_all' in website 1 not...` The first error occurs because the code line [1] renders the template `website_helpdesk_slides_forum.helpdesk_forums` (we will get this template id from `get_template_xml_id` method (at code line [2])), which inherits from `website_forum.forum_all_all_entries`. The inherited template expects the `_forums` variable to be defined. However, since we call the template directly without providing `_forums`, the template tries to access it and raises a KeyError. The second error occurs when rendering the `website_helpdesk_forum.forum_all` template, whose XML ID is retrieved using the `get_template_xml_id` method (see line [3]). This template does not actually exist, so when the system attempts to load it, the rendering process fails. This commit resolves the issue by rendering the `website_forum.forum_all` template instead of the template returned by `get_template_xml_id`, since the templates returned by that method either do not exist or cannot properly handle forums. The website_forum.forum_all template is designed to manage all forums, so it reliably covers the required use case. [1]: https://github.com/odoo/enterprise/blob/6658581828dcdc43ffc5823814a05cb936cd0500/website_helpdesk_forum/controllers/website_forum.py#L20-L22 [2]: https://github.com/odoo/enterprise/blob/6658581828dcdc43ffc5823814a05cb936cd0500/website_helpdesk_slides_forum/controllers/website_forum.py#L9-L10 [3]: https://github.com/odoo/enterprise/blob/6658581828dcdc43ffc5823814a05cb936cd0500/website_helpdesk_forum/controllers/website_forum.py#L24-L25 sentry-7159323242
This update corrects an inconsistency in how Odoo calculates available quantities for rental kits compared to standard products. Previously, the calculation was behaving differently depending on whether a product was rented. This fix standardizes the calculation, ensuring accurate availability figures for all rental kits, resolving a potential discrepancy in inventory reporting.
Original PR description
The behavior for computing _compute_qty_at_date fields(virtual_available_at_date, scheduled_date, forecast_expected_date, free_qty_today, qty_available_today) with kit products differs unexpectably with rentals vs. non-rentals. This change unifies their behavior by avoiding kit products (through display_qty_widget) field in sale_stock_renting. Steps to Reproduce: 1. Create 2 products, both with kit BOMs, one rental, one non-rental 2. Give components non-zero 3. Create a rental order with both products 4. Odoo Inspect / Studio add above fields to view 5. See computed difference opw-6141580
This update ensures that sales services from European companies to Northern Ireland customers are correctly excluded from the EC Sales List report. This change aligns with regulations and avoids inaccurate reporting. The update was specifically tested and implemented for the Belgium localization due to its unique handling of tax data.
Original PR description
…in EC Sales List The services sales done from a european company to a Northern Ireland company should not be included in the EC Sales List Report. It should however be the case for goods and triangular transactions. test is added in Belgium localization because only localizations have handlers using tax tags instead of taxes, and services/goods/triangular sales distinction can be made with these. task-6007931
This update ensures Odoo correctly sets the `toStateCode` field for SEZ e-waybill transactions, aligning with API requirements. Previously, this was missing, causing errors and preventing successful e-waybill submissions. This fix improves compliance and avoids potential disruptions to shipping processes.
Original PR description
For SEZ transactions, the e-waybill API requires `toStateCode` to be set to 99. Previously, this value was not enforced, leading to API errors. This fix updates the logic to derive `toStateCode` based on the partner's GST treatment. When the transaction is identified as SEZ, `toStateCode` is correctly set to 99, ensuring compliance with e-waybill requirements and preventing API failures. task-6117694