Friday, December 13, 2024
5 changes · 18.0
Resolved issues and error corrections
The Discuss sidebar now visually de-emphasizes inactive conversations so the active chat remains easier to focus on. Unread conversations still stand out enough to be noticed, improving usability without changing functionality.
Original PR description
Discuss sidebar items are too catchy, which is distracting when the core part of Discuss app is the conversation itself. As much as possible, conversation should be very visible while other elements are slightly less visible. This problem is even more pronunced when the sidebar is compact, because the avatars in sidebar are next to avatars of conversation, which is even more distracting. This commit fixes the issue by reducing opacity slightly on non-active sidebar items. Conversation that are unread and unactive have an in-between opacity so they are more visible than other read and non-active conversations but still have reduced opacity so that this is less distracting than the conversation itself. Backport of https://github.com/odoo/odoo/pull/190071
The HTML editor now correctly enables the remove formatting button when any selected content includes formatting, even if other selected text is plain. This makes editing formatted content more predictable and prevents users from being blocked from clearing styles in mixed selections.
Original PR description
When the selection contains formatted nodes among unformatted nodes, the remove format toolbar button should be available. This is not the case currently because the `hasAnyFormat` method, which is used to determine whether the button should be disabled, checks if **every** node in the selection is formatted. This commit fixes the issue by checking if **any** node in the selection is formatted instead. task-4385246
Fixes an error that occurred when users clicked the “Same payment” link after duplicating a confirmed payment. The payment screen now opens the related business document correctly, preventing an unexpected interruption in accounting workflows.
Original PR description
In the payment view, he `x2many_buttons` widget on `duplicate_payment_ids` calls the `action_open_business_doc`, but this method is not implemented on `account.payment`. This was not not a problem before 01b87f1230beac0568f4e3b1b76e547909506892 since a payment was always linked to a move, therefore we were calling the method from `account.move`. With this commit, we implement the `action_open_business_doc` in `account.payment`. Step: - Create a payment and confirm - Duplicate it - Click on the 'Same payment' hyperlink -> Error: "The method 'action_open_business_doc' does not exist on the model 'account.payment'" opw-4363907
Fleet contract status changes now use the same internal actions whether they are triggered automatically or by date updates. This makes custom behavior for opening or closing contracts easier to maintain and reduces the risk of inconsistent contract handling.
Original PR description
Since there are two mechanism that changes the status of a contract (a cron and the write of a date), we have to override 2 different places when we want to add a behavior on closing or opening of contracts. As there are already functions (action_expire, ...) that exist and are use in the write part, we also use them in the cron, so we'll have only one place where we need to override it. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue in Documents where opening a folder could fail after previewing a file, closing the preview, and switching views. Users can now continue navigating folders normally without encountering an error.
Original PR description
Steps to reproduce the traceback: - preview a file from the kanban view - close the preview - switch to list view - open a folder To Be: The folder should open correctly. Technical: The traceback happens because the 'getSelectedDocumentsElements' calls a querySelectorAll on the component root element without checking if it exists. Fixing the issue by making sure the component effectively have a root element before calling the method. Task-4373626