Daily updates from Odoo
Wednesday, July 20, 2022
11 changes · master
Enhancements to existing features
The Chilean electronic invoicing setup has been adjusted to stay compatible after email retrieval features were consolidated into the main mail system. This helps keep configuration records aligned and reduces upgrade or setup issues for affected deployments.
Original PR description
With linked community PR, the `fetchmail` module is moved into `mail` and so this commit adapts the changes by improving xml ids of the records that are now part of the `mail` module. task-2797458
Resolved issues and error corrections
This fix makes automated tests for spreadsheet date filters more consistent by using the right event when selecting dates. It reduces false test failures, helping development and releases stay predictable without changing user-facing behavior.
Original PR description
The tests using the new date picker were indeterministic. I'm pretty sure the problem was that the input was triggered by a click in the tests rather than by a "change" event. Odoo task 2925733
This update removes an unnecessary access restriction from Australian KeyPay settings. It prevents settings-related test failures and keeps the configuration behavior aligned with other accounting settings, with no expected impact for regular users.
Original PR description
Some settings are using the group "account.group_account_manager", which causes issue with a test on the settings. As this group is not really necessary, and no other accounting settings are using it, we can just remove it.
The app creator form now displays checkbox options with the correct spacing after the Bootstrap 5 update. This prevents confusing or misaligned fields when users configure a new model in Studio.
Original PR description
Since BS5, the checkbox input are visible, so we must set margin on the parent. Note in BS4 the input was hidden, and instead we rely on pseudo-element (`::before` and `::after`) Also removed `custom-control` class as not present in BS5 anymore.
This change fixes an unreliable automated test in the document spreadsheet area. It helps keep development checks stable so future updates can be delivered with fewer false alarms.
Fixed an issue where spreadsheets with a global filter set to a year could fail during export. Users can now export these spreadsheets reliably without the export crashing on year-based filters.
Original PR description
odoo-dev/enterprise@6645e89eacf8f40dcc46d9e4cb35bd41b9250220 introduced advanced year picking for global filter, but the year was returned as a year in the getter `getFilterDisplayValue()` instead of a string. This caused the export of the global filters to crash, since the export tried to call the method `.trim()` on a number. Odoo task 2896941
This fixes a styling issue where Odoo Studio used the browser's default font instead of the intended application font after the Bootstrap 5 migration. The change restores a consistent look in Studio, improving visual consistency for users without changing functionality.
Original PR description
Since BS5 migration, font in studio was not the same. This is because
it uses the SCSS variable `$font-family-base`, but in BS5 this variable
is set with:
```scss
$font-family-base: var(--#{$variable-prefix}font-sans-serif) !default;
```
but since it use `--#{$variable-prefix}` and there is no
`bootstrap_overridden.scss` for studio there was a missmatch and so no
font was set and use the default font set in the browser.
To avoid this, we set the `--#{$variable-prefix}` to empty to avoid
missmatch.Code cleanup and technical improvements
The dashboard view now relies on the standard onboarding banner that is already provided by default. This removes duplicate setup and helps keep dashboard behavior aligned with the rest of the system without changing the user experience.
Original PR description
Community: 9620deb7dc84b599b5085e942eb1eedbc3c85ecc
Miscellaneous changes
Before this commit, the printed layout of the report did not use any css. Trying to print the report would also produce a traceback because the subscription_id variable was not defined anymore. Forward-Port-Of: odoo/enterprise#29286
Original PR description
Before this commit, the printed layout of the report did not use any css. Trying to print the report would also produce a traceback because the subscription_id variable was not defined anymore. Forward-Port-Of: odoo/enterprise#29286
The diot report was completely wrong, as we did not have a refunds column, in which should have be present the amounts of the refunds paid with following taxes : IVA 16%, IVA 8%, IVA 0%, Whithheld taxes. We made a little refactor in _get_lines method in order to make it a little more readable, and allow to processcredit notes from above taxes on last column. Add also the refund column on diot and dpiva txt reports. opw-2733076 opw-2751671 Forward-Port-Of: odoo/enterprise#29614 F
Original PR description
The diot report was completely wrong, as we did not have a refunds column, in which should have be present the amounts of the refunds paid with following taxes : IVA 16%, IVA 8%, IVA 0%, Whithheld taxes. We made a little refactor in _get_lines method in order to make it a little more readable, and allow to processcredit notes from above taxes on last column. Add also the refund column on diot and dpiva txt reports. opw-2733076 opw-2751671 Forward-Port-Of: odoo/enterprise#29614 Forward-Port-Of: odoo/enterprise#29115
Previously, owl would not overwrite the value of an input when patched if the value computed in the render was the same as the previous render, even if the value in the DOM was changed (by the user or programmatically). This was fixed, but this can cause issues in components that relied on the old behaviour such as the timer header component. This commit simply puts the input value in a state and updates it as necessary, so that it is not lost on render. Forward-Port-Of: odoo/enterprise#2
Original PR description
Previously, owl would not overwrite the value of an input when patched if the value computed in the render was the same as the previous render, even if the value in the DOM was changed (by the user or programmatically). This was fixed, but this can cause issues in components that relied on the old behaviour such as the timer header component. This commit simply puts the input value in a state and updates it as necessary, so that it is not lost on render. Forward-Port-Of: odoo/enterprise#29626