Friday, July 19, 2024
5 changes · saas-17.4
Resolved issues and error corrections
Editing a message without attachments no longer creates an empty attachment record. This keeps message histories cleaner and avoids confusing users with placeholder files that were never uploaded.
Original PR description
When editing a message, even if there are no attachments, the post will create a null attachment. This is because the attachments from _message_update_content is an empty object rather than a list so that it is parsed as a record.  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures delivery location selection pages load their supporting code correctly and no longer fail because of an internal controller mistake. It helps customers complete checkout with delivery options more reliably.
Original PR description
This commit addresses those problems: - The location selector's controllers wrongly used `self`; - The controllers' folder was not imported into the `delivery` module.
This fix ensures Odoo correctly finds all IP addresses associated with a device, rather than only the most recent one. This improves accuracy for device tracking and related audit or troubleshooting activities without changing user workflows.
Original PR description
Issue: ------ The method which finds all the ip addresses linked to a device uses the `_read_group` method. This method can be called as part of the `res.device` model (which is the model that deduplicates `res.device.log` records and only keeps the most recent one for a device). As a result, we do not retrieve all ip addresses but only that of the last record. Solution: --------- Force the `res.device.log` model to perform the `_read_group`. It is also necessary to group together the "keys" that determine a given device in order to distinguish them when you want to retrieve all ip addresses linked to a device.
This fixes an issue where upgraded databases could have a disabled working hours view because payroll changes loaded in the wrong order. The view now uses the correct dependency, helping HR payroll screens continue to display reliably after upgrades.
Original PR description
Context: On an upgraded database we detected that the resource calendar inherited views where disabled, because they were not able to find parent element. The full timeline is as below: - 2021-01-01:…
Context: On an upgraded database we detected that the resource calendar inherited views where disabled, because they were not able to find parent element. The full timeline is as below: - 2021-01-01: commit odoo/enterprise@1d9fdd624497 introduced `hr_payroll.resource_calendar_view_tree` view - 2021-02-05: commit odoo/enterprise@0506d4e6fa18 introduced `hr_contract.resource_calendar_view_tree` view (with `contracts_count` field) - 2024-07-02: commit odoo/enterprise@1f03fb675922 updated `hr_payroll.resource_calendar_view_tree` view to add a field after `contracts_count` field. For databases that were update with each individual changes (at specified date), the `hr_payroll` inherited view will have a lower id than the `hr_contract` one and as such will be applied before (considering the standard view order). And following commit odoo/enterprise@1f03fb675922 this will raise a ValidationErorr: `Element '<field name="contracts_count">' cannot be located in parent view` This commit update `hr_payroll.resource_calendar_view_tree` view to inherit from the view that really add the `contracts_count` field.
This fixes an issue in Documents Spreadsheet where pivot table measures could miss their calculation method. Keeping a default calculation prevents inconsistent pivot behavior and helps users get reliable spreadsheet results.
Original PR description
Now the pivot's measures always have an aggragator, it cannot be undefined anymore. Task: 4052502