Monday, August 12, 2024
7 changes · 17.0
Resolved issues and error corrections
When a form is marked as non-editable, boolean fields inside related list or tag sections now correctly become read-only too. This prevents users from accidentally changing values in areas that should be view-only, keeping behavior consistent across the form.
Original PR description
Before this commit: When a form view was set to non-editable (edit="0"), its x2many fields could still contain editable boolean fields (e.g., Boolean Toggle). After this commit: Boolean fields within x2many fields are now also read-only when the form view is non-editable. Task-3802653 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix preserves missing text values when templates are modified through inheritance, avoiding unintended differences in the generated template structure. It helps keep existing templates stable and prevents unnecessary changes that could affect comparisons or tests.
Original PR description
When calling apply_inheritance_specs and moving a node (before after or inside), we merge the text content of the adjacents nodes. If the parent and target node both have no text, we should not set the text to an empty string. When a node has no text, it is serialized as follows: `<node/>` But if it has an empty string, it has the following representation: `<node></node>` In the linked PR, we now apply the studio inheritance manually, and since we use the resulting tree directly instead of parsing the result, the `remove_blank_text` option of the parser has no effect. This causes existing tests to show some difference. opw-3819667
Inventory managers are now granted read access to the accounting entries needed by inventory processes. This fixes cases where inventory users could not view or complete related stock accounting information due to missing permissions.
Original PR description
This PR will fix this issue [166958](https://github.com/odoo/odoo/issues/166958) There is no group access for the account.move, so system can't able to read the data from the account.move model, I grated the to the Inventory manager group. Now, user within the inventory access can able to read the data from the account.move model --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The problem is that the python logical operator "or" was translated Steps to reproduce: - add Romanian language - create an invoice --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Original PR description
The problem is that the python logical operator "or" was translated Steps to reproduce: - add Romanian language - create an invoice --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix gives Inventory Managers read access to the accounting entry records needed by inventory workflows. It prevents access errors when inventory users need to view or process stock valuation information linked to accounting moves.
Original PR description
This PR will fix this issue [166958](https://github.com/odoo/odoo/issues/166958) There is no group access for the account.move, so system can't able to read the data from the account.move model, I grated the to the Inventory manager group. Now, user within the inventory access can able to read the data from the account.move model. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
1) Start creating a tax 2) Set the 'Tax Computation' to 'Group of taxes' 3) In 'Definition' tab, select 'Add a line', choose to create a new tax 4) Jumpt to 2 Issue: Nested group of taxes are not allowed When adding the child tax users cannot choose group of taxes, but we can't block creation of just a specific type of taxes so we need to check the type afterward opw-4060955 Forward-Port-Of: odoo/odoo#175726 Forward-Port-Of: odoo/odoo#173889
Original PR description
1) Start creating a tax 2) Set the 'Tax Computation' to 'Group of taxes' 3) In 'Definition' tab, select 'Add a line', choose to create a new tax 4) Jumpt to 2 Issue: Nested group of taxes are not allowed When adding the child tax users cannot choose group of taxes, but we can't block creation of just a specific type of taxes so we need to check the type afterward opw-4060955 Forward-Port-Of: odoo/odoo#175726 Forward-Port-Of: odoo/odoo#173889
### Steps to reproduce: - Install Timesheet and Time-off modules - Let the time-off validation creates a timesheet - Create a time off for an employee and validate it - Archive this employee ### Current behavior before PR: After archiving an employee you will still have the timesheets related to his upcoming leaves even when you are closing all of his activities. This is happening because when archiving an employee we are just updating the state of his hr.leave to refuse without unl
Original PR description
### Steps to reproduce: - Install Timesheet and Time-off modules - Let the time-off validation creates a timesheet - Create a time off for an employee and validate it - Archive this employee ### Current behavior before PR: After archiving an employee you will still have the timesheets related to his upcoming leaves even when you are closing all of his activities. This is happening because when archiving an employee we are just updating the state of his hr.leave to refuse without unlinking the timesheets https://github.com/odoo/odoo/blob/15.0/addons/hr_holidays/wizard/hr_departure_wizard.py#L23 ### Desired behavior after PR is merged: While archiving an employee we are calling the 'action_refuse' method where it will update the state of the employee's leaves and also will unlink the timesheet related to those leaves. opw-4070684 Forward-Port-Of: odoo/odoo#175923 Forward-Port-Of: odoo/odoo#175725