Wednesday, December 17, 2025
4 changes · 19.0
Resolved issues and error corrections
This fix prevents Point of Sale sessions on multiple devices from crashing when an order canceled on one device is still being processed on another. It ensures pricing information is ready before prices are recalculated, improving reliability for cashiers using shared POS setups.
Original PR description
- When using POS on multiple devices and when an order was canceled from an other device, the order prices computation was leading to a traceback. - Now we ensure that the prices data is initialized before triggering a recompute of all prices. task-id: 5411637 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Copying rich content from read-only Knowledge views into editors now keeps more formatting intact. This prevents table cell background colors and similar styling from being lost when users paste content into places like project tasks.
Original PR description
To make it possible to properly copy DOM elements across editors, the `application/vnd.odoo.odoo-editor` mimetype was introduced in the `ClipboardPlugin`. However, this was not used inside the `HtmlViewer`. Because of this, some content formatting could be lost when copying elements from an `HtmlViewer` to an editor. This commit solves this by also invoking the code that fills the clipboard in `ClipboardPlugin` when content is copied in an `HtmlViewer`. Steps to reproduce: - Insert a table in Knowledge - Set a background color on a few cells - Use the "lock" feature of Knowledge (inside a dropdown the menu on the right) - Select the entire table - Copy/paste it in a project task => The background colors in the cells were lost task-4017841 Forward-Port-Of: odoo/odoo#240207 Forward-Port-Of: odoo/odoo#238655
This update fixes an error in the Mexican payroll module that caused incorrect period end calculations when creating pay runs with schedules like '10 Days' or 'Bi-weekly'. The fix ensures that pay runs are generated with the correct period end date, aligning with updated payroll standards. This improves the accuracy of payroll processing for Mexican companies.
Original PR description
Bug: When we create a new pay run for a mexican company and we select the schedule "10 Days", "14 Days", "Bi-weekly" or "Bi-monthly", the end of the period is computed incorrectly. Cause: The standard method changed but it wasn't updated in the mexican payroll module. Fix: Change the signature of the method to match the one in hr_payroll. Task: 5421825
This update resolves an issue where users without HR permissions couldn't submit 360 feedback. A recent security change now requires access checks on related data, and this fix uses `sudo()` to bypass the check when necessary, allowing these users to complete the process. This ensures all users can participate in 360 feedback assessments.
Original PR description
**Version:** - 19.0 **Steps to reproduce:** - As an administrator, create an appraisal and assign an appraiser who has no HR permissions (regular user role) - Log in as the appraiser. - Attempt to submit a 360 feedback. - An access error is raised. **Issue:** - The 360 feedback wizard fails due to missing access rights when sending the feedback. **Cause:** - https://github.com/odoo/odoo/pull/217277/commits/4a822785ca850c7ae5b21039536333276b2c61af - A recent ORM change now enforces a read-access check on the comodel when writing to Many2many fields. The 360° feedback wizard writes to an M2M field referencing hr.employee, but appraisers (non-HR users) lack read rights on hr.employee, causing the new security check to raise an AccessError. **Fix:** - During create(), check whether the current user has access to rights on hr.employee. If not, create the wizard with `sudo()` so it can create and write the required records without raising an access error. task-5261938