Thursday, March 6, 2025
4 changes · saas-18.1
Resolved issues and error corrections
Receipts without order lines no longer display the misleading prompt to start adding products. This avoids confusion when settling customer accounts in Point of Sale, where receipts are view-only and cannot be edited.
Original PR description
When settling the user account from pos_settle_due, we show a receipt with no order (as expected), but with an empty state saying "Start adding products"! Now we don't show the empty state on a receipt, since the user cannot edit a receipt anyway. This bug has been reported while using the pos_settle_due module, however, the fix has been made generic and hence been implemented in the point_of_sale module. (Note, this same bug has been fixed in 17.0 with https://github.com/odoo/odoo/pull/197256, and it was fixed in 17.2 till 18.0 with https://github.com/odoo/odoo/pull/184646) opw-4430325
This fix prevents live chat sessions from accidentally reverting their message loading status after updates are received in real time. It helps avoid unnecessary message loading and keeps the chat experience more reliable for users and support teams.
Original PR description
When a live chat session is created, the "isLoaded" field of the thread comes from the server to avoid loading messages if it's not needed. However, sending this information on the bus can rollback the newest value after message fetch. This PR ensures this information is not sent through the bus. This issue was discovered in 18.2 as websockets are enabled during tours. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Mail discussion and chat compact display settings now update immediately across open browser tabs. This keeps the user experience consistent without needing to reload pages or manually adjust each tab.
Original PR description
Before this commit, some local settings were not properly synced in crosstab: - discuss sidebar compact mode was only visible on reloading the page. - chat hub compact mode was only affected the tab…
Before this commit, some local settings were not properly synced in crosstab: - discuss sidebar compact mode was only visible on reloading the page. - chat hub compact mode was only affected the tab that triggered the compact mode. The problem of discuss sidebar compact comes from lack of responsiveness from change in local storage value, which this commit fixes with `onStorage` in DiscussApp model. Note that settings model had already this implementation, but it made a typo: the `this` in `onStorage` could be the raw record instead of reactive record. This is fixed by registering the `onStorage` in the `static new`. For the ChatHub compact mode, usually triggering this mode is intended for reduced footprint of chat windows when navigating on the webclient, including opening new or existing tabs. This means the compact mode should be applied on all tabs at once. This commit fixes it by using a similar technique as discuss sidebar compact mode to sync its state immediately accros all tabs. 
This fixes a small issue in the Indian localization reports where extra information was being sent to a credit purchase message. The change helps avoid errors and keeps the process reliable without changing user-facing workflows.
Original PR description
The method _l10n_in_edi_get_iap_buy_credits_message does not have the company_id parameter. This commit removes the redundant argument to ensure correctness and prevent unnecessary parameter passing.