Odoo Changelog — 2025-07-13

Sunday, July 13, 2025

3 changes · 18.0

Improvements(1)

Enhancements to existing features

[IMP] *: whitelist l10n modules for invisible fields

Core18.0l10n_arl10n_brl10n_chl10n_cll10n_cnl10n_ecl10n_eg_edi_etal10n_es_edi_facturael10n_es_edi_siil10n_es_edi_tbail10n_fr_hr_holidays

Several country-specific localization modules are now excluded from a technical validation that was not being run for them consistently. This prevents repeated automated test failures without changing how users work with these localizations.

Original PR description

Most l10n modules are only installed during the standalone l10n job, which does not run `test_uncommented_invisible_field`. As a result they fail the test in every version where it was introduced.

- sort the whitelisted modules
- add the l10n that currently fail, as we don't want to fix them
- revert change adding a bunch of comments in views

#localization#testing#maintenance

Bug Fixes(1)

Resolved issues and error corrections

Update account_move_views.xml

PR #218744

Core18.0account

The Post button on accounting entries will now be hidden when posting is not allowed, such as for already posted or auto-scheduled entries. This removes a confusing option from the screen and better aligns the interface with the system's actual rules.

Original PR description

[FIX] account: ensure `hide_post_button` is declared in form view

The `hide_post_button` field is used in the `invisible` condition of the "Post" (`action_post`) button on `account.move` form views. However, it was not explicitly declared in the view, which caused the button to be always visible even when it should be hidden.

This commit adds the missing field to the form view (invisible), so the `invisible` condition is properly evaluated by the client UI.

This fixes a UI inconsistency where the Post button appears for posted or auto-scheduled entries, despite backend logic preventing their posting.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:

#accounting

Refactoring(1)

Code cleanup and technical improvements

[REV] *: revert #85750

PR #90126

Enterprise18.0documents_l10n_hk_hr_payrolll10n_ar_edil10n_au_hr_payrolll10n_au_hr_payroll_accountl10n_be_codaboxl10n_be_hr_payroll_dimonal10n_br_avatax

This pull request reverts a previous broad change that was creating repeated maintenance conflicts during version updates. The intended checks will instead be handled in tests, reducing disruption while keeping room for future improvements.

Original PR description

Change is noisy, conflicts on every forward port, and doesn't preclude adding more errors.

Whitelist on the test side instead.

Most l10n modules are only installed during the standalone l10n job, which does not run `test_uncommented_invisible_field`. As a result they fail the test in every version where it was introduced. - sort the whitelisted modules - add the l10n that currently fail, as we don't want to fix them - revert change adding a bunch of comments in views

[FIX] account: ensure `hide_post_button` is declared in form view The `hide_post_button` field is used in the `invisible` condition of the "Post" (`action_post`) button on `account.move` form views. However, it was not explicitly declared in the view, which caused the button to be always visible even when it should be hidden. This commit adds the missing field to the form view (invisible), so the `invisible` condition is properly evaluated by the client UI. This fixes a UI inconsistency where the Post button appears for posted or auto-scheduled entries, despite backend logic preventing their posting. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: