Friday, June 20, 2025
6 changes · saas-18.3
Resolved issues and error corrections
This fixes an error that appeared when editing the Suggested Accessories toggle in the website editor. The affected website sales add-ons now point to the correct updated template, so users can edit the option without hitting a crash.
Original PR description
Traceback when editing the toggle button, through the website editor The element '<xpath expr="//del">' cannot be located in the parent view Description of the issue/feature this PR addresses: This…
Traceback when editing the toggle button, through the website editor The element '<xpath expr="//del">' cannot be located in the parent view Description of the issue/feature this PR addresses: This issue has happened because of the standard change in the module. Current behavior before PR: Traceback click on Suggested Accessories, the toggle button through the website editor. in v18.2 the module [website_event_sale](https://github.com/odoo/odoo/blob/saas-18.2/addons/website_event_sale/views/website_sale_templates.xml#L24) and [website_sale_loyalty](https://github.com/odoo/odoo/blob/saas-18.2/addons/website_sale_loyalty/views/website_sale_templates.xml#L128) is inherit the cart_line and target the [node](https://github.com/odoo/odoo/blob/saas-18.2/addons/website_sale/views/templates.xml#L2087) is available in the view. But in version 18.3 this node is move to other [template](https://github.com/odoo/odoo/blob/saas-18.3/addons/website_sale/views/templates.xml#L2341) that's why the node is not find. Desired behavior after PR is merged: After the change i target the new [template](https://github.com/odoo/odoo/blob/saas-18.3/addons/website_sale/views/templates.xml#L2435) so the node is now find. Issued PR https://github.com/odoo/odoo/pull/190720 [OPW](https://www.odoo.com/odoo/project/70/tasks/4864959?debug=1) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The priority field in project sub-task forms now has the right amount of space for the updated star rating. This prevents the priority control from appearing cramped or misaligned, improving clarity for users managing project tasks.
Original PR description
This commit fixes the size of the priority field in the project_task_views form view's sub-tasks because it was not updated properly when the widget got 2 more stars. task-4881973
Rescheduling a meeting activity now also updates the linked calendar event date. This prevents users from seeing outdated meeting times in the calendar after changing an activity schedule.
Original PR description
Steps to reproduce ================== 1. Create a meeting activity on any record. 2. Go to `My Activities`. 3. Use the `reschedule` button to reschedule it tomorrow. 3. Go to calendar and check the date --> Date is still the same as when the activity was created After this PR ================= This commit updates the meeting accordingly. Task-4813092
Reloading a conversation while replying to an older message no longer causes the mail composer to crash. This improves reliability for users drafting replies, especially when the page is refreshed or restored with partial message data.
Original PR description
Before this commit, when a composer had a reply-to on a message. Reloading the page would lead to the following crash: ``` TypeError" undefined is not an object (evaluating 'ctx['props'].composer.replyToMessage.thread.notEq') ``` Steps to reproduce: - post 2 messages in conversation - start replying to the oldest message - page reload => crash This happens because when page reloading the composer is recovering its content, including the reply-to message. The reply-to composer recovery only contains the `messageId`, hence the crash above. When the reply-to message of composer is the last one this would not crash thanks to thread fetched data that also contains the last message data, which has proper link of message to thread. This commit fixes the issue by guarding message.thread relation in template, as the UI must be robust against partial knowledge of data.
The bank statement screen no longer shows an empty reconciliation button when no reconciliation models are available. This prevents users from clicking a broken option and makes the interface clearer.
Original PR description
Before this PR: An empty reconciliation button was displayed on the bank statement line when no reconciliation model existed, causing an error upon clicking. After this PR: That empty button is no longer shown if there are no applicable reconciliation models, avoiding the error and improving UI clarity. task-4876367
The Accounting app now hides a bank reconciliation button when its related model has been deleted. This prevents users from seeing an unlabeled button and avoids an error when reviewing bank transactions.
Original PR description
This error occurs because the model ID was deleted, but the button still references it. As a result, the button is displayed without a label, and clicking it leads to an error. Steps to reproduce: --- - Install the `Accounting` module - Accounting > Bank > Models (under Reconciliation) and delete all reconciliation models. - Go to Bank Transactions > Dropdown any statement line > click on button (without label) Traceback: --- `ValueError: Expected singleton: account.reconcile.model()` This commit resolves the issue by hiding the button when `model.id/label` is null. sentry-6674669584