Friday, September 12, 2025
5 changes · 17.0
Resolved issues and error corrections
Event searches now show consistent results whether users choose a dropdown suggestion or press Enter. Events that match the search term in their description are included on the results page, reducing confusion and helping visitors find relevant events.
Original PR description
Purpose ======= Making sure that, when typing a search term, all the results displayed in the search bar dropdown are visible on the page when clicking Enter. Specification ============= Previously, the search bar dropdown was displaying all the events where the name or description matched the search term. However, when clicking Enter, only the events where the name matched were displayed on the page (the ones where only the description matched were ignored). Fixing the issue by considering the description in the event search options. Task-5039221 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes how closed WebSocket connections are handled during internal test cleanup. It prevents one expected connection-closed situation from being reported as a different, misleading error, helping keep automated test results clearer and more reliable.
Original PR description
Followup to 16.0-closed-in-stop-xmo: the condition in `stop` is a `hasattr`, so we need to delete `self.ws` not set it to `None`. Setting it to `None` means the condition passes then blows up as soon as we try to use it, which means we "just" converted all the old `WebSocketConnectionClosedException` to an `AttributeError`. https://runbot.odoo.com/odoo/error/231446 Forward-Port-Of: odoo/odoo#226267
This update adds the missing SZJ product code required by Hungary's official NAV electronic invoicing specification. It helps ensure Hungarian invoice data can be classified correctly and stay aligned with regulatory documentation.
Original PR description
Description of the issue/feature this PR addresses: In the official NAV XML 3.0 documentation (available at: https://onlineszamla.nav.gov.hu/dokumentaciok page 123), according to the list of possible product codes, there is an 'SZJ' code that is missing. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
DIN5008 invoice reports no longer show the customer phone number in the address block, and customer VAT details are moved out of that address section. This keeps the report layout cleaner and better aligned with the intended DIN5008 presentation.
Original PR description
This commit removes the phone number from the DIN5008 report layout. The customer's VAT is also no longer displayed in the customer's address section. The VAT is moved to another section. Description of the issue/feature this PR addresses: Current behavior before PR: The customer's phone number and VAT are displayed in the customer's address in the DIN5008 report layout. Desired behavior after PR is merged: The customer's phone number is no longer displayed and VAT moved to another section in the DIN5008 report layout. opw-5049074 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The product margin calculation now uses net invoice amounts when calculating average sales prices. This prevents tax-included and tax-excluded invoice lines from being mixed together, giving businesses more reliable margin reporting.
Original PR description
The price_unit of a account.move.line can be with or without tax. The sale_avg_price should be either incl. or excl. tax. To ensure the avg price is always excl. tax the price_subtotal can be used. Forward-Port-Of: odoo/odoo#199209