Daily updates from Odoo
Friday, May 16, 2025
9 changes
2 changes
Resolved issues and error corrections
The IoT log download button now responds properly when selected instead of showing an error. This helps users access device logs reliably when troubleshooting IoT issues.
Original PR description
The iot download logs button widget js code didn't have an onClick method which resulted in an error when you press it:
```
UncaughtClientError > OwlError
Uncaught Javascript Error > Invalid handler (expected a function, received: 'undefined')
Occured on 80350261-saas-18-3-all.runbot177.odoo.com on 2025-05-15 12:30:59 GMT
OwlError: Invalid handler (expected a function, received: 'undefined')
Error: Invalid handler (expected a function, received: 'undefined')
at Object.mainEventHandler (https://80350261-saas-18-3-all.runbot177.odoo.com/web/assets/debug/web.assets_web.js:14945:23)
at HTMLButtonElement.listener (https://80350261-saas-18-3-all.runbot177.odoo.com/web/assets/debug/web.assets_web.js:9281:20)
```
This PR fixes this issue by properly definining an "onClick" method
task-4797770The point of sale IoT setup no longer shows a "no IoT box found" notification when newer connection wizards are available. This avoids confusing staff with an outdated warning during device setup.
Original PR description
Since the PR https://github.com/odoo/enterprise/pull/83066 which adds new wizards for IoT Box connection it is no longer necessary to display "no iot box found" notification. This PR removes this notification which could still be seen
1 change
Resolved issues and error corrections
The planning interface now keeps the planned date range with allocated hours field at a consistent width. This prevents visual inconsistencies and makes scheduling information easier to read for users.
Original PR description
This commit takes advantage of changes made in https://github.com/odoo/odoo/pull/209075 to fix the same issue for the PlannedDateRangeWithAllocatedHours field as well. task-4751837
6 changes
Resolved issues and error corrections
The portal and project sharing message box no longer automatically takes focus when a page opens, preventing unwanted cursor placement for users. The change keeps project sharing messages aligned with backend behavior so users see the expected message prompt.
Original PR description
PR #189568 removes the focus from the project sharing composer by setting the `inFrontendPortalChatter` to true, which goes against the whole idea of having this parameter. The correct fix is to remove the `autofocus` (prop) from the composer, because it was only there to keep the focus on the project sharing composer. This commit undoes the change in the mentioned PR and removes the `autofocus` from the portal chatter composer. Consequently, the composer placeholder in project sharing becomes the one related to `note`, so this commit adds `type="'message'"` to the composer to ensure consistency with the backend when sending a message.
Barcode scanning in Point of Sale no longer opens the product configuration popup when a product has only one available attribute option. This makes checkout faster and avoids unnecessary cashier interruptions.
Original PR description
Before this commit, scanning the barcode of a product with attributes set to never creation type, but with only one option available, would still trigger the product configuration popup. opw-4754801 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Event badges with long event names now keep the QR code separate from the badge text. This prevents printed badges from becoming unreadable and helps event check-in materials remain usable.
Original PR description
Steps to reproduce: 1. Go to Events. 2. Create a new event with a long name. 3. Add a product. 4. Print the "Badge Example". Issue: When printing a badge from an event with a long name, the QR code overlaps or clips the information above it, making the badge unreadable. Cause: The issue is due to the large font size used for the event name. Solution: Reduced the font size of the event title to fs-5 to ensure enough spacing is maintained between the text and the QR code, avoiding layout overlap. opw : 4783750 Before FIX:  After FIX: 
This fixes a problem in the website live chat test flow that was causing automated build checks to fail. It helps keep the release validation process stable without changing the user-facing live chat experience.
Original PR description
Runbot Build Error: https://runbot.odoo.com/odoo/runbot.build.error/111747 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Changing the style of selected link text in the editor no longer causes an error. This makes formatting links more reliable for users working in apps such as To-do.
Original PR description
Steps to Reproduce: 1. Go to the To-do module. 2. Create a link. 3. Select the entire content using Ctrl + A. 4. Change the font style from 'Normal' to another (e.g., 'Header 1'). 5. A traceback is…
Steps to Reproduce: 1. Go to the To-do module. 2. Create a link. 3. Select the entire content using Ctrl + A. 4. Change the font style from 'Normal' to another (e.g., 'Header 1'). 5. A traceback is thrown, although the link’s font style is changed. Description of the issue/feature this PR addresses: - The issue was caused by the presence of a `FEFF` (zero-width no-break space) character inside the selected text. This caused a conflict during selection restoration after the font style change. The clean handler was being triggered after the font change attempt, which led to an invalid cursor state. Current behavior before PR: - A Traceback occurred when changing the font style of a selected link text. Desired behavior after PR is merged: - The clean handler is now explicitly called before the font change tries to restore the cursor, avoiding the invalid range or selection error. task-4743390 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents a Kenya payroll accounting test from failing when the separate SHIF payroll component is not installed. It improves reliability for single-app deployments without changing payroll behavior for end users.
Original PR description
## Version: 17.0+ ## Issue: Test (introduced by task 4457038) fails on Single App because of missing dependency. Relies on SHIF_AMOUNT https://github.com/odoo/enterprise/blob/ffb0aa8d7aad913328bb0b585197172da4e838b3/l10n_ke_hr_payroll_shif/data/hr_salary_rule_data.xml#L46C1-L47C1 runbot-159825