Tuesday, April 22, 2025
3 changes · saas-18.1
Resolved issues and error corrections
The reset shortcuts used when preparing IoT box images now point to the latest downloaded code instead of sometimes failing to find the expected branch. This reduces setup errors for development or origin-based image builds and helps keep device preparation predictable.
Original PR description
`odoo_origin` and `odoo_dev` aliases used to reset odoo code on a dev/origin branch were sometimes returning an error not finding the fetched branch. They are now resetting on FETCH_HEAD to ensure the reset on the latest fetched branch.
Installing Event Products, Sales, or Sales Timesheets no longer fails if the default Service product category was previously deleted. The change helps users recover from configuration changes without hitting a blocking installation error.
Original PR description
Currently a `ParseError` arises when the user installs the modules after deleting the `Service` Category in Invoicing. Steps to reproduce: --- - Install `Invoicing` application (without demo data). -…
Currently a `ParseError` arises when the user installs the modules after deleting the `Service` Category in Invoicing.
Steps to reproduce:
---
- Install `Invoicing` application (without demo data).
- Invoicing > Configuration > Categories > Delete `Service`
- Now installs the modules (event_product, sale, sale_timesheet)
Traceback:
---
```
ValueError: External ID not found in the system: product.product_category_services
ParseError: while parsing /home/odoo/src/odoo/saas-18.1/addons/event_product/data/event_product_data.xml:4, somewhere inside <record id="product_category_events" model="product.category">
<field name="parent_id" ref="product.product_category_services"/>
<field name="name">Events</field>
</record>
```
The error occurs because the user deleted the category, and then installed the modules, that reference the missing product category.
This commit resolves the error by providing a False value for the field if the product category is missing.
sentry-6235143606
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prFixes an error that could occur when users clicked Get Critical Path in the project task Gantt view after removing planned start dates. This keeps project planning usable and prevents an unexpected crash in a specific task-dependency workflow.
Original PR description
Currently, a traceback occurs when the user clicks critical path in tasks gantt. To reproduce this issue: 1) Install Project and add the `Use Task Dependencies` group to the current user 2) Open the…
Currently, a traceback occurs when the user clicks critical path in tasks gantt. To reproduce this issue: 1) Install Project and add the `Use Task Dependencies` group to the current user 2) Open the list view of the project 3) Enable the `Task Dependencies` to any one project 4) Now remove all the start dates from the Planned Date for all tasks 5) Open the Gantt view of the tasks and add a task 6) Refresh the page, and click the `Get Critical Path` button Error:- ``` KeyError: 24 ``` https://github.com/odoo/enterprise/blob/c9a753fce85dfb09dc413831993e63c7736d258a/project_enterprise/models/project_task.py#L1544 From the above line, the traceback is occurring because the `path_last_task` will take the value from the sorted_tasks's first record. But we don't have any `planned_date_begin` in any task except the one we added in the Gantt view. So the first task which is `path_last_task` will not execute further because of this, https://github.com/odoo/enterprise/blob/c9a753fce85dfb09dc413831993e63c7736d258a/project_enterprise/models/project_task.py#L1529-L1531 This leads to the above traceback when we compare the value of the `path_last_task` from the `total_time` with the current task. https://github.com/odoo/enterprise/blob/c9a753fce85dfb09dc413831993e63c7736d258a/project_enterprise/models/project_task.py#L1544 We can resolve this issue by taking the `path_last_task` if only the task contains `planned_date_begin`. sentry-6327461743