Wednesday, January 29, 2025
7 changes · saas-18.1
Resolved issues and error corrections
This fix restores a reliable way for developers and testers to simulate read-only database behavior locally without needing a real replica. It reduces confusion in configuration handling and helps prevent accidental read-only behavior when no replica is intended.
Original PR description
A regression introduced by #193728 removes the support for local read-only testing without a real replica. Before this change, it was possible to test a readonly like behavior by providing a `--db_replica_host=` to the command line. The empty replica will still use a socket connection to the main server, but would work as if a replica host was given. The distinction between an empty string and False was used to make it work Since b1f7be518e2075c546bcedc0f4ba6dd62dff3c8f the default is not False but an empty string, leading to the readonly behavior even without a replica. This pr proposes to introduce a new dev mode flag to enable the replica mode, without False vs empty string check avoiding some confusion.
The mail avatar stack now shows the overflow counter on top of the previous avatar instead of hiding it. This makes participant counts clearer when many people are shown in a compact avatar list.
Original PR description
The avatar stack displays several avatar on top of each other. When there are too many avatars to display, a counter is shown. However, this counter is hidden by the previous avatar. In order for the stack to work, each item should have an higher z index than the previous one. It's correctly done for avatars but not for the counter. This pr fixes the issue. | Before | After | | ------------- | ------------- | |  |  |
Live chat users can now confirm the close confirmation dialog with the Enter key as expected. Focus also returns to the message composer when cancelling, making it easier to continue typing or reopen the confirmation with the keyboard.
Original PR description
Before this commit, the Enter hotkey did not work to confirm the CloseConfirmation in livechat. This happened because: - The `keydown` event is currently captured by the chat window not the CloseConfirmation component because the focused element is not properly detected. - `useAutofocus` doesn't detect the focus target element because it checks only for the main tree DOM root, not the shadow root. This PR changes the `useAutofocus` to handle the shadow roots and puts the focus on the chat window composer on cancel so it's more effective in case the user needs to type or use Esc to reopen close confirmation.
This update cleans up recently added emoji picker code by using clearer method names and ensuring mouse events are passed correctly. It is a low-risk maintenance fix that helps keep the interface reliable and easier to maintain.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/195236 PR above add new methods to emoji picker for nice little feature. Commit had minor issues that this PR fixes: - names were poor: onMouseEnter => onMouseenterEmoji (mouseenter event on an emoji) onMouseLeave => onMouseleaveEmoji (mouseleave event on an emoji) currentSelectedEmoji => activeEmoji (simpler and consistent with existing attributes on this component) - ev of mouseenter and mouseleave were not propagated correctly to the handler methods (even if not used... yet?)
This fixes how hierarchy-based searches handle text input, so matching records are found before their related hierarchy is resolved. It helps prevent missed results in filters that use names or other text values instead of exact record IDs.
Original PR description
Domains such as `[('id', 'child_of', 'some_str')]` should search the corecords using ilike before resolving the hierarchy. Adding tests for this use case.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis fixes a small visual issue where icons and labels in mail message and chat action menus did not line up neatly. The change makes the interface look more polished and easier to scan without affecting functionality.
Original PR description
They were slightly misaligned visually, which didn't look great. This is fixes by replacing `.align-items-center` by `.align-items.baseline`    
A bug in Manufacturing Planning Schedule forecast details was fixed so the system now uses the correct purchase order line field. This prevents an error that could interrupt users when viewing or calculating forecast quantities.
Original PR description
Currently, a traceback occurs while executing the compute method `_compute_quantity_and_label`. The error is occurring from the below line https://github.com/odoo/enterprise/blob/272f945e1ca427316fd7d08b7bb611074bed2a6f/mrp_mps/wizard/mrp_mps_forecast_details.py#L40 This is because in `purchase_order_line`, the `product_uom` field is renamed to the `product_uom_id` from the below commit. https://github.com/odoo/odoo/pull/186250/files#diff-5684edced9bdfc98021a85de4c6cdf691ea7add74e56ab50334a1d7db9ef4224R33 So indeed an attribute error will occur from the above mentioned line. Error:- ``` AttributeError: 'purchase.order.line' object has no attribute 'product_uom' ``` By giving the valid attribute we can resolve this issue. sentry-6248119730, 6240577568