Wednesday, May 28, 2025
8 changes
1 change
Resolved issues and error corrections
Helpdesk tickets now keep their existing action buttons when the live chat button is added. This prevents users from losing quick access to other ticket actions while still allowing them to view related chats.
Original PR description
Before this commit, the adding of View chat stat button has erased the other stat buttons instead of adding the stat buttons after the existing ones in helpdesk.ticket form view. This commit adds the view chat stat button after the other stat buttons displayed instead of replacing them.
1 change
Resolved issues and error corrections
This update keeps the AI assistant feature compatible with recent platform changes by using the new content-selection method. It helps avoid failures when users interact with selected page content through the AI tool.
Original PR description
Community PR: https://github.com/odoo/odoo/pull/209228 The Community side of this PR removes `getTraversedNodes` and `getSelectedNodes` and replaces them with `getTargetedNodes`. This accordingly replaces a call to `getTraversedNodes` with one to `getTargetedNodes`. task-4809282
6 changes
Resolved issues and error corrections
When users edit an existing review, the popup button now changes to clearly show that they are updating the review. This removes confusion in the review editing flow for portal and eLearning course pages.
Original PR description
**Before this PR:** The button label in the popup does not update when a user tries to edit a review. **Technical**- The button label updates only during the widget initialization, as it is handled in the willStart function. https://tinyurl.com/2derk498 **After this PR:** The button label in the popup correctly updates to 'Update Review' when a user edits a review. **Task**-4677251
This fix prevents an error when loading Attendances sample data after a previously referenced employee was deleted. It ensures the related HR skills sample data can load correctly, helping users set up or test HR modules without interruptions.
Original PR description
Currently, an error occurs when loading sample data for **Attendances** if a referenced employee record has been deleted by the user. **Steps to reproduce:** - Install the `hr_appraisal` module…
Currently, an error occurs when loading sample data for **Attendances** if a referenced employee record has been deleted by the user.
**Steps to reproduce:**
- Install the `hr_appraisal` module without demo data.
- Load sample data for **Appraisals**.
- Navigate to **Employees** and delete record for **Emma Granger**.
- Install `hr_attendance` module and load sample data for **Attendances**.
- Observe the error.
**Error:**
`ValueError - ParseError('while parsing /home/odoo/src/odoo/saas-18.2/addons/hr_skills/data/scenarios/hr_skills_scenario.xml:209, ...`
The error occurs because the method at [1] tries to load the `hr_skills_scenario.xml` file, which references a deleted `employee_id` [2], resulting in a parsing failure.
[1] - https://github.com/odoo/odoo/blob/547327f30d2d4bf778b9d358dbea4b133d55188a/addons/hr_skills/models/hr_employee.py#L49
[2] - https://github.com/odoo/odoo/blob/5c1db495828a7fe8c6ec987de432b1916ad32922/addons/hr_skills/data/scenarios/hr_skills_scenario.xml#L210
This commit ensures that all the referenced data is loaded properly, preventing errors due to missing references.
Sentry - 6426462322This update prevents an error when a user enters a VAT number on a new customer record before saving it. It keeps the customer form usable by safely handling missing commercial partner information until the record is saved.
Original PR description
Currently, An error occurs when adding a `vat` number in res_partner form view without saving a record. Steps to produce: - Install the `account` and `web_studio` modules - Create a customer, Add field name 'commercial_partner_id' in customer form view. - Enter a `VAT` number and click anywhere in the form view before saving the record. `ValueError: Expected singleton: res.partner()` An error occurs when the system is attempts to access a value of `commercial_partner_id` at [1], but it is not available. Link 1: https://github.com/odoo/odoo/blob/c87acdcfa48b1d8aa66bb5d27d58e3edb70a86ba/addons/account/models/partner.py#L670 To prevent this error, add a condition to check if value of `commercial_partner_id` is not available. then set `invoice_edi_format` to False. Sentry-6383383350 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now export attachment file content in XLSX format without hitting an error screen. This corrects a broken internal reference introduced by a prior rename, improving reliability of the export workflow.
Original PR description
When the user tries to export a file of attachment in xlsx format, A traceback will appear. Steps to reproduce the error: - Open attachments > Upload a file that does not contain base64-encoded content - Select that file > Actions > Export > Export Format: XLSX > Add File content(raw) field > Export Traceback: ``` AttributeError: 'ExportXlsxWriter' object has no attribute 'field_names' ``` In this commit: https://github.com/odoo/odoo/commit/a4e04518a437f09d6a10e25a35900c4adfe11dc6 ``field_names`` is renamed to ``fields``. https://github.com/odoo/odoo/blob/0e98b684834cf9e1d646e55599e7bc00aa5997f0/addons/web/controllers/export.py#L231 Here, ``field_names`` is still used. So, it will lead to the above traceback. sentry-6096581800 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Corrected a spelling mistake in the UrbanPiper product label from “Is Alchoholic” to “is Alcoholic.” This improves clarity and professionalism in product information shown or managed through the point-of-sale integration.
Original PR description
In this commit: --------------- - Corrected the label from `Is Alchoholic` to `is Alcoholic`. task- 4826438
This fix prevents an error when creating a Mexican payroll payslip if the period end date is removed. Payroll users can continue preparing payslips without the screen failing due to missing date information.
Original PR description
The system failed to retrieve `worked_days.payslip_id.date_to` because user remove end period Steps to Reproduce: 1. Switch to `My Mexican Company`. 2. Go to Payroll > click Payslips > To Pay > Click New 3. Select Employee from the selection 4. Remove end date from period (Right One). Error: `TypeError: unsupported operand type(s) for -: 'bool' and 'datetime.date'` Solution: Ensure that if worked_days.payslip_id.date_to, start_date, end_date are not present then continue the flow Sentry - 6473512002