Daily updates from Odoo
Wednesday, February 4, 2026
4 changes · saas-18.2
Enhancements to existing features
This update enables IoT devices connected to our Point of Sale system to function correctly without requiring a secure HTTPS certificate. A new setting allows requests to use HTTP instead, simplifying the connection process for IoT boxes. This improves reliability and reduces setup complexity.
Original PR description
Community PR: https://github.com/odoo/odoo/pull/246781 This is a backport of odoo/enterprise#100331. Since odoo/odoo#235702, there is a `point_of_sale.use_lna` system parameter. When it is set, ePOS requests will use HTTP instead of HTTPS, and the `targetAddressSpace: "local"` option is used in the `fetch` request. This bypasses the need for a HTTPS certificate. This commit adds the same functionality to all IoT requests from the POS. This should allow the IoT box to function correctly without a HTTPS certificate. task-5353672 Forward-Port-Of: odoo/enterprise#106183
Resolved issues and error corrections
This update resolves an issue where salary attachments would display an empty employee field after an employee was archived. The fix ensures that salary attachments accurately reflect the current employee status, preventing data inconsistencies and improving reporting accuracy. This change was made to maintain data integrity within the payroll system.
Original PR description
Steps To Reproduce: Create a salary attachment for an employee. Archive that employee. The corresponding salary attachment has an empty `Employee`. Issue: `employee_ids` many2many field doesn't take archived records into consideration, So when an employee is archived, it leads to emptying the record. Fix: Add active_test context to field definition and domain to form view of salary attachment so the employee remains on salary attachment and for new record creation, so it doesn't take archived employees. task-5438657 Forward-Port-Of: odoo/enterprise#106275 Forward-Port-Of: odoo/enterprise#102985
This update resolves an issue where the fuel card benefit was incorrectly enabled in the salary configurator when no company car was selected. The fix ensures the field is initially disabled until a car is chosen, preventing inconsistencies and simplifying the user experience. This improves data accuracy and reduces potential errors.
Original PR description
On first load of the salary configurator, the fuel-card benefit could appear enabled even when no company car was selected. The dependency logic reacted to in-page changes but did not initialize the field correctly on page load. Initialize the fuel-card field from the current car selection and keep it non-selectable until a car is chosen to prevent inconsistent packages. task-5156562 Forward-Port-Of: odoo/enterprise#97119
This update corrects an issue where project forms accessed through SmartButtons were initially displayed as uneditable. The fix removed a redundant setting that was causing this behavior, ensuring users can now properly interact with project forms. The root cause of the original setting is currently unknown.
Original PR description
Issue: When navigating to any form view related to an FSM Project via
SmartButtons, they are loaded as uneditable
Solution: Remove "edit":False in _update_action_context method
Note: It is unknown why this was added in the first place, since
removing it does not cause any crashes
opw-5413753
Forward-Port-Of: odoo/enterprise#105225