Tuesday, February 4, 2025
8 changes · 17.0
Resolved issues and error corrections
This fixes an upgrade issue for Spanish Facturae electronic invoicing when moving from Odoo 16 to 17. The update now ignores tax records that are not available yet, preventing upgrade failures while keeping the expected default tax behavior.
Original PR description
Tax account_tax_template_s_iva0_g_i was added in 17.0. Init hook will load the data from account.tax-es_common.csv (_l10n_es_edi_facturae_post_init_hook) when upgrading from 16.0 and fail because account_tax_template_s_iva0_g_i does not exists yet. Removing account_tax_template_s_iva0_g_i from account.tax-es_common.csv prevent the bug and l10n_es_edi_facturae_tax_type will still be set to 1 as it is the default value. Runbot error: https://runbot.odoo.com/odoo/runbot.build.error/114680
The reset password page now uses the correct form behavior, so users no longer get stuck with an incorrect loading spinner during password reset. This helps prevent confusion and makes account recovery smoother.
Original PR description
Currently signup.js also defines SignUpForm, which overrides the reset password behavior. This bug is not present in 16.0, so I used the same name for the registry that is being used in 16.0.
This fixes an issue where loading translations for several accounting chart templates at the same time could reuse the first template’s data for all others. Businesses using multiple localization templates should now get the correct translated accounting setup for each template.
Original PR description
Fixes a small issue when loading translations of multiple chart templates at once. An update to that method added a parameter with the same name as a local variable, and the way it has been done means that the template_data used in each subsequent loop will always be the ones from the first loop only, effectively ignoring the other chart templates. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The HR Plans smart button now opens with the relevant department already selected, reducing manual setup for users. If no plan exists yet, it opens the form to create one directly, making the workflow smoother.
Original PR description
In this PR, - Set the default department for the Plans smart button. - If there is no plan, it will open the form view. Task-4356557
This fixes an automated Belgian payroll test that could get stuck when Chrome’s newer headless mode handled contract signing more strictly. The test now uses the correct street address field and removes obsolete form-filling steps, improving reliability without changing business functionality.
Original PR description
During the upgrade to the "new" headless mode of Chrome (default for v128+), an issue with the tours "hr_contract_salary_tour" and "hr_contract_salary_tour_2" was detected. In a nutshell, in those…
During the upgrade to the "new" headless mode of Chrome (default for v128+), an issue with the tours "hr_contract_salary_tour" and "hr_contract_salary_tour_2" was detected. In a nutshell, in those tours, during the signing of the contract, the "street" field wasn't pre-filled and leaving it empty. The step-by-step filling system (e.g. the "Next" button on the left) was confused and put the date in the street field (sic). For some reason, the "old" Chrome headless mode - while encountering the same issue - didn't complained with it... But the "new" mode (which is actually closer to the actual GUI behavior of Chrome) got stuck at those steps. This commit fixes this issue by using the `private_street` field (which contains the actual street name) instead of the `private_street2` field (which is often empty). Once done, a second issue was detected as the step filling the computation of "58/4" didn't match (even wrongly) any empty field anymore. This commit simply removes those unused steps.
The Mexican Point of Sale localization tests now include VAT where required. This helps keep automated checks aligned with real tax requirements and prevents false test failures in validation runs.
Original PR description
Adding VAT in test for testing MX l10n in PoS Error Runbot: 111329, 111328
Users can now select and delete behavior elements in Knowledge without triggering an error. This prevents interruptions while editing Knowledge content and makes the deletion action work as expected.
Original PR description
Previously, attempting to select and delete a knowledge_behaviour element resulted in a traceback. Task-4210216