Wednesday, July 13, 2022
11 changes · master
Resolved issues and error corrections
The Settings screen now keeps the Save and Discard actions visually aligned when they appear inside a mobile dropdown. This makes the mobile settings experience cleaner and reduces confusion when users manage configuration changes on smaller screens.
Original PR description
In the settings view, on mobile the save and the discard button are wrapped in a dropdown. As the save button is primary and the discard is secondary when there are wrapped in the dropdown there are miss aligned as there padding are not the same. This commit, avoid to change the padding on mobile of these elements. Steps to reproduce: * Open Odoo (on Mobile) * Go in Settings * Open the dropdown => BUG -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adjusts the layout of the media selection dialog so fields line up more cleanly when several inputs appear on the same row. It helps make the editor interface easier to read and use, with no expected impact on business workflows.
Original PR description
Add some classes to improve the alignment. Quite difficult to deal with as we have a lot of inputs on the same line. Follow of odoo/odoo#95725 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change fixes an internal sales module test that could fail when the Sales app is installed by itself. It ensures the test user has the right access to update units of measure, helping keep automated quality checks reliable without changing customer-facing behavior.
Original PR description
When `sale` is installed alone,
the test fails because it changes the field `product_uom`
which is invisible in the view because the user executing the test
doesn't have the appropriate group.
```
FAIL: TestSaleOrder.test_fiscalposition_application
Traceback (most recent call last):
File "/data/build/odoo/addons/sale/tests/test_sale_pricelist.py", line 292, in test_fiscalposition_application
line.product_uom = uom
File "/data/build/odoo/odoo/tests/common.py", line 2179, in __setattr__
assert not self._get_modifier(field, 'invisible'), \
AssertionError: can't write on invisible field product_uom
```This update adjusts an internal test so it works correctly when only the accounting accountant module is installed. It helps keep automated checks reliable and prevents false failures during development or upgrades.
Original PR description
This is about the same than
d6ad39abba12d8da302e0ecc9c24e064b1768300
but with account_accountant installed
```
FAIL: TestFormCreate.test_create_res_partner
Traceback (most recent call last):
File "/data/build/odoo/odoo/addons/base/tests/test_form_create.py", line 35, in test_create_res_partner
partner_form.property_account_payable_id = property_account_payable_id
File "/data/build/odoo/odoo/tests/common.py", line 2179, in __setattr__
assert not self._get_modifier(field, 'invisible'), \
AssertionError: can't write on invisible field property_account_payable_id
```A bug in expense splitting prevented users from selecting all eligible purchase taxes in some cases. This fix removes that limitation so split expense lines follow the same tax handling as regular expenses.
Original PR description
Task 2850882 modified the behaviour of expenses to support working with all purchase taxes, regardless of their 'price included' configuration. We missed a domain on the split lines though, so it was impossible to use 'all taxes' when splitting an expense. This commit resolves that limitation/oversight.
The web interface now better recognizes filter operators when displaying domain selector rules. This prevents confusing placeholders from appearing, so users see clear filter descriptions such as "Name like M" instead of an unknown operator.
Original PR description
Before this commit, it happened that the domain selector couldn't find the operator linked to the field. This commit adds a fallback on the existing operators to find an operator that matches. for example the domain `[["name", "like", "M"]]` gave `Name ? "M"`, now it correctly gives `Name like "M"`.
This fix restores the intended visual styling for the accounting journal dashboard after a previous change caused the custom layout to stop applying correctly. It helps users see the dashboard as designed, improving consistency and readability without changing business workflows.
Original PR description
Since 4f984568e139d8da448018af12ef79005e317cf6, the specific css style was not applied correctly to the journal dashboard.
Fixes an invoicing issue where orders containing note or section lines could fail if no account was specified for those non-financial lines. This helps users create invoices from such orders more reliably without requiring extra hidden accounting values.
Original PR description
When an invoice line has a display_type, account addon is expecting account_id=False in vals. Replacing the normal dict access with a `get` will fix the error when invoicing with note/section lines without explicitly specifying the `account_id` to be false. **Old description which is still relevant:** When an orderline has a note, invoicing fails because of missing account_id key in the invoice line vals. For notes and section lines to work, we need to explicitly specify that the account_id is false. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The account setup screens now show the account type selector correctly again after recent changes to account type handling. This helps accounting users choose valid account categories without confusion or broken interface behavior.
Original PR description
Task 2917456 After the change in the account_type field in the account.account, the old selection widget didn't work. Fixing the selection widget and adding it back to the account_type field. As account types cannot be custom anymore, the account types within the hierarchy can be hardcoded. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix restores a payroll processing method that was accidentally removed from Belgian payroll. It prevents issues in the related attendance payroll module that depends on this behavior.
Original PR description
…method PR https://github.com/odoo/enterprise/pull/25998 inadvertenly removed the _preprocess_work_hours_data_split_half method in the hr_contract model in l10n_be_hr_payroll. The method is overriden in l10n_be_hr_payroll_attendance and thus required
The payment matching screen has been corrected to use the updated account type names introduced by recent accounting changes. This prevents the matching view from breaking when users reconcile receivable or payable payments.
Original PR description
Task 2916588 Due to the recent account types refactoring, the payment matching view was breaking, as now receivable should be asset_receivable, payable -> liability_payable Fix to correct values