Friday, May 23, 2025
5 changes · saas-18.1
Resolved issues and error corrections
The mobile quick reaction button now opens the emoji picker in a full-width bottom dialog instead of squeezing it into the message list area. This makes adding reactions on phones easier and avoids a cramped, hard-to-use interface.
Original PR description
Before this commit, when a message has at least 1 reaction, using the quick reaction button in mobile displayed the emoji picker that shared the viewport of message list. This makes it hardly…
Before this commit, when a message has at least 1 reaction, using the quick reaction button in mobile displayed the emoji picker that shared the viewport of message list. This makes it hardly practical. This happens because the `useEmojiPicker()` in message reactions provide a ref, and this ref in mobile is used as a target to mount the emoji picker. This feature is useful for discuss composer to place emoji picker nicely under the composer input. In desktop the ref is used for click target of popover. In practice the passing of ref in mobile is niche use-case: most of the time it should open in bottom screen as a dialog in a similar fashion as popover. This commit fixes the issue by making 1st param of `useEmojiPicker` only act as the toggler part . In mobile to provide the container of emoji picker, one need to call `open(ref)` explicitly. Task-4800688 From click there:  Before  After 
This fixes live chat routing so old call records are cleaned up before deciding whether operators are available. It helps prevent agents from being incorrectly treated as busy, improving the chance that visitors can reach support when someone is actually free.
Original PR description
Follow up of https://github.com/odoo/odoo/pull/193597 Starting from 18.1, the unavailable operators (due to being in call in particular) are excluded from available_operator_ids, rather than filtered afterwards. This means the gc will not be called if all operators are in call, even though the goal was to remove potentially obsolete calls.
The Documents app now displays folder hierarchies correctly when users arrive from other apps such as Fleet or Project. The “All” folder remains visible, making it easier for users to find and browse documents consistently.
Original PR description
Issues:
i) When coming from another app (Fleet, Project, etc.), the control panel
does not correctly display the subfolders.
ii) The “All” folder should always be displayed.
Technical Reason:
i) Correctly set folder_id as False for documents whose parent folder is
inaccessible, ensuring a clean and accurate folder hierarchy in the
search panel.
ii) It was intended, add a condition when coming from other modules 'All'
should not display.
After this commit:
i) Correctly display folders in hierarchy in a search panel when coming from other modules.
ii) 'All' folder should always be displayed.
Task-4669259Users who open a spreadsheet they cannot access, or one that no longer exists, are now redirected instead of seeing a confusing error screen. This improves the experience when shared links are invalid or permissions do not allow access.
Original PR description
Before this commit, if a user attempted to open a spreadsheet they lacked access to or that did not exist, they would get a traceback due to improper error handling. This commit resolves the issue by handling server errors when fetching the spreadsheet and redirecting the user to the documents app. Steps to reproduce: - Create a spreadsheet with Mitchell Admin. - Copy a hyperlink. - In another browser, log in as Marc Demo and paste the hyperlink. - You get a traceback and you don't understand what's going on. task-4551255
The Luxembourg annual VAT declaration appendix now opens without triggering an error. This restores access to the affected tax reporting section so users can complete the annual VAT declaration workflow normally.
Original PR description
Repro steps: 1.Install l10n_lu_reports module 2. Go to Reporting > Tax Return > Annual VAT Declaration 3. Click on `Appendix to Operational Expidenture` 4. You will get a traceback error Cause: As of this PR in 18.1: https://github.com/odoo/enterprise/pull/70280 The function `registerCustomComponent` changed in 2 ways: 1. It now expects a module name 2. It registers the component by its name These changes were not applied in l10n_lu_reports module hence causing the error of the component not being found in the registery This commit solves this issue by applying those changes in l10n_lu_reports module task-4816146