Tuesday, February 25, 2025
9 changes · saas-18.1
Resolved issues and error corrections
This fix changes how certain IAP JSON-RPC endpoint errors are reported, replacing noisy error stack traces with clearer warnings. This reduces unnecessary log noise while still keeping administrators informed when validation or transaction-related issues occur.
Original PR description
Currently, an error occurs in the log when a ValidationError or InFailedSqlTransaction error occurs when calling the JSON-RPC endpoint in IAP. error: `ConnectionError: null` This is because [1] added logger.exception that logs every error in the log when it appears. This commit will use the logger warning to print a warning in the terminal instead of the exception when a ValidationError or InFailedSqlTransaction error occurs. [1] - https://github.com/odoo/odoo/commit/a1477d1d00adb928b149f8e019f65c00f75ef129 sentry-6059323528
Fixed a display issue where form view scrollbars could appear on top of open chat windows, making conversations look partially covered. Chat windows now remain properly layered above the page content for a cleaner, less confusing experience.
Original PR description
Before this commit, when chat windows are open above form view, the scrollbar of form view was shown above the chat window. Steps to reproduce: - open project task with pad aside (1080p+ screen) -…
Before this commit, when chat windows are open above form view, the scrollbar of form view was shown above the chat window. Steps to reproduce: - open project task with pad aside (1080p+ screen) - open 2 or 3 chat windows - type many lines in project task pad to make form view scrollable - (optional) scroll on the form view => the scrollbar is above the chat windows This happens from a recent change [1] that increased the z-index of statusbar and ribbon of form view. This had the side-effect of also making z-index of scrollbar as high as their new z-index, which is `$zindex-sticky: 1020`. Chat window z-index was `$zindex-dropdown + 1: 1001`, slightly higher than the z-index of document views elements that were also negatively affecting chat windows [2]. This commit fixes the issue by increasing even more the z-index of chat windows, from 1001 to 1020. This puts them at the same level as sticky. Task-4604254 Before  After  [1]: https://github.com/odoo/odoo/pull/197581 [2]: https://github.com/odoo/odoo/pull/198362
The Point of Sale flow now waits until an order deletion is fully complete before allowing the register action to continue. This prevents accidental creation of a new order during fast automated or user interactions, improving reliability in the register workflow.
Original PR description
runbot-error-id: 111973 After deleting an order, the runbot was clicking so fast on the register button that it was creating another order. This commit checks that the deletion of the order is fully finished before clicking on register. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes a translation conflict around the word "register" in Point of Sale. It helps ensure translated labels are clearer and less likely to be confused with similar terms used elsewhere in Odoo.
Original PR description
Description of the issue/feature this PR addresses: Translation issue Current behavior before PR: The term "register" confilicts with other terms in other modules Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The follow-up partner screen now displays the send button in line with the overdue invoices section. This small visual fix makes the page easier to read and helps users find the main action more naturally.
Original PR description
The send button wasn't align with the overdue Invoices above, now he is. task-4582381 Linked:https://github.com/odoo/enterprise/pull/79446
The Discuss command palette now avoids showing the same direct message conversation twice when it is both recent and has mentions. This keeps important mentioned conversations prioritized while making the chat list clearer and less confusing for users.
Original PR description
Before this commit, a conversation that was both recent and contained mentions could be displayed twice in the discuss command palette. This was the case with DM chats. An item should be present only…
Before this commit, a conversation that was both recent and contained mentions could be displayed twice in the discuss command palette. This was the case with DM chats. An item should be present only once in the command palette, and if a conversation has both mentions and is recent, it should be present only in the most important category "mentions". The problem occurs because duplicate mentioned and recent conversations are tracked on mentioned channels, using either the conversation or the persona of correspondent for DM chat. The check on mentioned persona was mistakenly omitted, thus a DM chat could be present in mentions and recents. This commit fixes the issue by properly checking whether the persona of DM chat was already in "mentions", so that it's not elligible in the "recent" category if that's the case. task-4510209 Before <img width="658" alt="Screenshot 2025-02-24 at 14 07 44" src="https://github.com/user-attachments/assets/fab6e6bb-fead-4c31-9fd4-4a2a3a4e895f" /> After <img width="661" alt="Screenshot 2025-02-24 at 14 07 52" src="https://github.com/user-attachments/assets/cf70035a-42b0-47df-96a3-1a95580d18a2" />
This fix prevents an error when deleting certain attachments in the Indian GSTR reporting module. It removes an unnecessary dependency-related call, helping the module work reliably whether or not related electronic invoicing features are installed.
Original PR description
_unlink_except_government_document() is only defined in account_edi, which is not a dependancy of this module... but we don't need to call super for an ondelete constraint. runbot error: 114255
Fixed an issue where scanning an unknown barcode or QR code in Point of Sale could show an error instead of opening the product creation flow. This keeps barcode lookup workflows working smoothly when staff need to add missing products during a POS session.
Original PR description
**Steps to reproduce:** - Install "Point of Sale" - Go to "Settings" - Enter the API Key for "barcodelookup.com" - Open a POS session - Scan a QR code not linked to any product **Issue:** The following error is raised: The action "point_of_sale.product_product_action_add_pos" does not exist. **Cause:** The action has been renamed to "product_template_action_add_pos". opw-4584711
The follow-up partner view now aligns the send button correctly with the overdue invoices section. This small visual fix makes the screen cleaner and easier for users to read when managing customer follow-ups.
Original PR description
The send button wasn't align with the overdue Invoices above, now he is. task-4582381 linked:https://github.com/odoo/odoo/pull/198529