Monday, July 28, 2025
7 changes · 17.0
Resolved issues and error corrections
Users who have permission to manage pricelists can now archive them even if they do not have access to loyalty programs. This removes an unnecessary permission blocker and helps teams maintain pricing records without extra administrative rights.
Original PR description
Finetuning of d20b6f6407f49f9bff8cf3677b2fe07cb3588298, if a user had access rights on the pricelist model but not on loyalty programs, he wouldn't be able to archive a given pricelist. Has already been fixed in the aforementionned commit forward-port, starting from 18.2. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents an error when a website editor user changes a button into a regular link and then saves it. The editor now correctly hides button-specific controls when the element is no longer a button, avoiding a disruptive save failure.
Original PR description
Problem: Saving the button snippet after changing its type to a link throws an error because `snippet_key` is `undefined`. Cause: The button snippet editor should be disabled if the button is changed…
Problem: Saving the button snippet after changing its type to a link throws an error because `snippet_key` is `undefined`. Cause: The button snippet editor should be disabled if the button is changed to a link. However, `updateOptionsUIVisibility` is only triggered on click events. In this case, the element type changes through the editor itself, not by clicking, so the UI isn't updated accordingly. Solution: Trigger a `click` event on the link element programmatically to call `updateOptionsUIVisibility` and hide the button snippet editor when the element is no longer a button. Steps to reproduce: - Drop a button snippet - Click inside the button to edit - Notice the Button snippet editor appears - Change the type to "Link" instead of "Primary" - The Button snippet editor is still visible - Click the floppy disk icon (save) in the snippet editor -> A traceback occurs opw-4936796 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Before this change, the VAT Content section in Argentinean Legal PDF was always shown as "VAT Content" although the user has Spanish as its language. With this change will show the correct translation: "IVA Contenido" when printing the PDF report in Spanish. ### **Description of the issue/feature this PR addresses:** Missing Spanish translation of "VAT Content" column in the Argentinean Legal PDF Report 1. Install Argentinean - Accounting module 2. Install Spanish language 3. Log int
Original PR description
Before this change, the VAT Content section in Argentinean Legal PDF was always shown as "VAT Content" although the user has Spanish as its language. With this change will show the correct…
Before this change, the VAT Content section in Argentinean Legal PDF was always shown as "VAT Content" although the user has Spanish as its language. With this change will show the correct translation: "IVA Contenido" when printing the PDF report in Spanish. ### **Description of the issue/feature this PR addresses:** Missing Spanish translation of "VAT Content" column in the Argentinean Legal PDF Report 1. Install Argentinean - Accounting module 2. Install Spanish language 3. Log into to one of the demo Argentinean Companies: (AR) Responsable Inscripto 4. Create a customer invoices of type "B" 5. Go to the partner and change the Language to Spanish 6. Return to the invoice and print the PDF 7. Check that the VAT Content section is not translated. ### **Current behavior before PR:** <img width="572" height="407" alt="image" src="https://github.com/user-attachments/assets/e28e609e-2cd2-4ace-9509-f969692ec893" /> ### **Desired behavior after PR is merged:** The "VAT Content section should appear as "IVA Contenido" when printing the report in Spanish. opw-4938520 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Corrected the spelling of Huancayo in the Peru localization city data by removing an accidental space. This helps ensure addresses and location records display the correct city name for Peruvian users.
Original PR description
The Huancayo has an extra space in the name. Instead of Huancayo it is written Hua ncayo in the csv file. opw-4947526 Forward-Port-Of: odoo/odoo#219888
This fix prevents an error when adding a country to a customer address if the fiscal country setting is empty. It helps users continue creating or updating customers without interruption in the India localization setup.
Original PR description
Currently, an error occurs when trying to add a country to the customer address, and fiscal Country is not available. Step to produce: - Install the ```l10n_in``` module. - Open the settings of an invoice, Search 'fiscal Country', and remove a country from it. - Create a new customer and try to add country to the address. ```TypeError: argument of type 'bool' is not iterable``` An error occurs when the system checks conditions for fiscal country code at [1] but it is (False) not available. Link [1]: https://github.com/odoo/odoo/blob/c172695afc2af8d75fd3b0d3172b28600eec7005/addons/l10n_in/models/res_partner.py#L37 To resolve the issue, add a condition to ensure that 'fiscal Country' is not empty before checking a condition of it. Sentry-6101261474 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue in the Swiss payroll ELM transmission area where some payroll-related forms could fail when default values were prepared automatically. The change helps keep automated checks stable and reduces the risk of interruptions when users create these records.
Original PR description
https://runbot.odoo.com/odoo/runbot.build.error/115307
This update fixes a test setup issue in the Avalara tax integration by removing a reference to a sales-related field that is not always available. It helps keep single-app test builds stable without changing customer-facing tax features.
Original PR description
This issue was introduced with [26018](https://github.com/odoo/enterprise/pull/26018) It was later fixed in master with [48435](https://github.com/odoo/enterprise/pull/48435) but this didn't apply to v16. Removed reference to field `invoice_policy` as this module doesn't depend on sales and this breaks single app test build on v16. Runbot - [163226](https://runbot.odoo.com/odoo/error/163226) Forward-Port-Of: odoo/enterprise#90651