Friday, June 6, 2025
7 changes · saas-18.3
Resolved issues and error corrections
Chat windows now have a stronger shadow so conversations stand out better from the page content behind them. This makes messages easier to read and reduces visual confusion when chat overlaps other information.
Original PR description
Before this commit, when there was some content under chat windows, this was hard to read chat window conversations and content below. This happens because the chat windows lack visual separation from the content below: everything looked flat. There was a slight `.shadow-sm` on chat window but it barely contributed to separation with background. This commit fixes it by using stronger `.shadow` instead. Before  After 
The website module now handles malformed website domain names more safely instead of letting them stop an upgrade. This reduces upgrade failures caused by invalid domain settings and helps affected customers complete migrations more reliably.
Original PR description
It's possible that the `hostname` obtained from `website_domain` is invalid, for instance: ``` website_domain='https://.com' hostname='.com' ``` Attempt to encode it with `idna` will raise an error: `UnicodeError: encoding with 'idna' codec failed (UnicodeError: label empty or too long)` There's a few upgrades to 18.3 failing due to this: [Traceback Group](https://upgrade.odoo.com/odoo/action-178/2029) Tested with [upg-2847175](https://upgrade.odoo.com/odoo/action-150/2847175)
Bank statement lines now correctly match a customer or vendor even when the same partner has multiple linked bank accounts with the same account number. This prevents valid matches from being missed during bank reconciliation, reducing manual correction work.
Original PR description
There was a corner case where a single partner should match a statement line but would not. The case was when the statement line account number matches multiple accounts that are linked to the same active partner. This commit fixes this issue by relying on the number of partners instead of the number of banks while matching. task-4826477
The EC Sales List warning now more accurately identifies truly duplicated VAT numbers. This prevents businesses from seeing unnecessary duplicate VAT alerts when a customer has both invoices and refunds in the same reporting period.
Original PR description
Fixed the computation of `is_vat_duplicated` to avoid false positive in case of partners having both invoices and refunds in the selected period.
Point of Sale IoT auto-configuration now prefers USB-connected receipt printers over network printers when assigning a printer. This helps improve receipt printing reliability during POS setup by choosing the more dependable connection type first.
Original PR description
Currently when auto-configuring IoT with pos printers we take the first available receipt printer we assign to PoS we chose. However if the printer is usb-connected it should take priority over network printers for the reliability reasons. task-4853231
Opening the return kanban now applies its expanded group setting only to that specific return view. This prevents unrelated kanban views from being unintentionally changed, keeping other workflows consistent for users.
Original PR description
Before when we would open the return kanban, it would set for every other kanban the variable MAX_NUMBER_OPENED_GROUPS to max integer. This is not what we want, we only weant to restrict that to the Return Kanban Model only not every relational model.
Portal users will no longer see the Invite button when sharing Knowledge articles. This prevents them from triggering an access error for an action they are not allowed to use, improving the sharing experience.
Original PR description
Currently, the "Invite" button is visible to portal users. When a portal user clicks this button, the system attempts to open a wizard using the `knowledge.invite` model. However, because portal users lack access rights to this model, the system raises an "Access Error". Steps to reproduce: 1. Log in as a portal user 2. Open an article 3. Click on the "Share" button 4. Click on the "Invite" button => Traceback: Access Error on the model `knowledge.invite` To fix the issue, we will simply hide the "Invite" button for the portal user as it was the case before the permission panel refactoring. See: odoo/enterprise#76261 Task-4636494