Daily updates from Odoo
Thursday, December 5, 2024
15 changes
2 changes
Resolved issues and error corrections
The Social Demo module now reuses existing standard records instead of creating duplicate copies. This reduces test database inconsistencies and helps avoid unexpected issues when the demo module is installed accidentally or for testing.
Original PR description
Although `social_demo` is a strong independent module it's a bit odd that it partially duplicates a bunch of data from `base` and `product`, and if it gets installed (possibly by mistake) into a database for testing, some tests don't cope well with the issue. Remove the duplicated records and just reference the base ones. Leave `product_product_4d` as it's either novel to `social_demo` or was removed from `product` since it was initially duplicated.
The barcode scanning flow now shows a correctly spelled and grammatically improved error message when a scanned barcode is not found. This makes the receipt process clearer for users and reduces confusion during warehouse operations.
Original PR description
Barcode --> Operations --> Receipts --> NEW Scan a barcode that doesn't exist in the DB ie: "5449000000996" The current error message's spelling and grammar are off. opw-4307102
9 changes
Resolved issues and error corrections
The chat window’s conversation name and avatar are now easier to click because a small unresponsive area beside them was removed. This keeps the same visual spacing while making the more-actions interaction feel more reliable for users.
Original PR description
When mouse-hovering more actions (the conversation name & avatar), the clickable zone had a small dead zone on the left. This comes from `mx-1`, which put good spacing but had the unintentional deadzone spacing. This commit replaces the `mx-1` by equivalent extra padding, thus removing the deadzone while keeping the overall same spacing. Before / After <img width="391" alt="Screenshot 2024-12-04 at 16 50 52" src="https://github.com/user-attachments/assets/323d8ece-2965-49c3-acc6-d2e4590c1fb2"> <img width="390" alt="Screenshot 2024-12-04 at 16 50 38" src="https://github.com/user-attachments/assets/97ba506d-8fa4-4825-957a-5f22be9910fe"> Difference (red) <img width="1911" alt="Screenshot 2024-12-05 at 12 44 00" src="https://github.com/user-attachments/assets/aa7c9079-f2b4-467d-8e1f-58f2ce9b8da1">
Opening a shared project task no longer automatically focuses the chatter area. This prevents unwanted scrolling, especially on mobile, so portal users land on the task details as expected.
Original PR description
… sharing The objective is to remove the focus on the chatter whenever a task is opened in project sharing. This aimed initially to avoid the automatic scroll to the bottom in mobile view. As a note: the Chatter component in project_sharing refers to the mail/chatter, however as project module also includes the portal/static/src/chatter/core/chatter_patch.js, Chatter template in project is overrided leading to autofocus triggering. To replicate: 1. Share a project with tasks to a user with Edit permission. 2. login with portal user and open the project portal view 3. Open a task. The focus should no longer be set on the Chatter automatically. 3-b. Also on Mobile, when opening a task the sreen should not scroll to the chatter. task: 4353290 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Messages that are not grouped together now show both the day and time, such as "Today at 10:00" or "Yesterday at 08:00". This makes busy conversations easier to follow when many messages were posted on the same day.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/188665 PR above changed "X days ago" on messages by time, so that the exact time can be viewed without requiring mouse-hovering. Indeed, after some…
Follow-up of https://github.com/odoo/odoo/pull/188665 PR above changed "X days ago" on messages by time, so that the exact time can be viewed without requiring mouse-hovering. Indeed, after some time, the rounding of the relative time tend to show relative day when message was posted but the datetime was lacking. However, by only showing time, when many messages are posted the same day, this becomes unclear to know the day the messages were posted, as the date sections do not have any sticky behaviour on viewport. Putting sticky behaviour on date section require more style change, which may probably be reserved for future improvements. This commit fixes the issue by showing the date of non-squashed messages, e.g. "Today at 10:00", "Yesterday at 08:00", "Dec 2 at 20:00", etc. Before / After <img width="194" alt="Screenshot 2024-12-05 at 11 42 33" src="https://github.com/user-attachments/assets/1c9cd1c9-d8d8-4700-88d1-2dba239c87c4"> <img width="265" alt="Screenshot 2024-12-05 at 11 42 18" src="https://github.com/user-attachments/assets/359a308c-a380-49af-986f-ab13839f013b">
The livechat window buttons now adapt their hover color to the customized chat header color instead of using a fixed white or dark style. This keeps actions visible and easier to use across default, white, dark, and customized livechat themes.
Original PR description
Chat window action mouse hover effect was hardcoded for white and dark theme. In livechat, the header color can be customised. With the default colors (purple background and white text), the hover…
Chat window action mouse hover effect was hardcoded for white and dark theme. In livechat, the header color can be customised. With the default colors (purple background and white text), the hover effect had white background, which made the action not visible. This commit fixes the issue by using a slight color invert when mouse hovering the action of a chat window, so that the color is slightly different from header color while keeping icon color distinguishable. Before / After <img width="390" alt="Screenshot 2024-12-04 at 17 10 23" src="https://github.com/user-attachments/assets/f4993b05-5f69-4de6-8423-fc69f7b2bdd7"> <img width="393" alt="Screenshot 2024-12-04 at 17 09 37" src="https://github.com/user-attachments/assets/1c867d1a-8df8-46e3-ae04-e68154e169a5"> White and dark theme are more catchy as a result: Before / After (white theme) <img width="394" alt="Screenshot 2024-12-04 at 17 11 16" src="https://github.com/user-attachments/assets/e29578ca-8b15-45d9-828a-aa65b43a6b23"> <img width="384" alt="Screenshot 2024-12-04 at 17 11 40" src="https://github.com/user-attachments/assets/025b2145-b783-4ab0-bf94-44fe24d32d81"> Before / After (dark theme) <img width="389" alt="Screenshot 2024-12-04 at 17 11 05" src="https://github.com/user-attachments/assets/be50f34d-7468-415b-b365-734fed3e9001"> <img width="387" alt="Screenshot 2024-12-04 at 17 11 59" src="https://github.com/user-attachments/assets/8a0a8c09-c179-4e1e-befe-0fcdff3a181c">
The automated tour for Knowledge article commands has been updated to work with the current editor behavior. This helps ensure the Knowledge app remains properly tested and reduces the risk of unnoticed issues reaching users.
Original PR description
In this commit, we fix knowledge_article_commands_tour by adapting the steps that concern the odoo editor in order to reactivate this tour.
This fix ensures key document-related automation is restored correctly when upgrading to version 18.0 if customers previously removed related document tags. It also prevents those restored records from being recreated again on later updates, reducing unexpected changes after the upgrade.
Original PR description
server actions that use document tag should be noupdate as well because document tag records are noupdate, and they could be deleted by clients. possible steps to reproduce: 1) make a database 17.0 2) delete document tags 3) upgrade the database to 18.0 Document tags and server actions should be recreated in upgrade scripts when upgrading to 18.0 if they are missing. Setting the noupdate=1, makes sure that they are not recreated on subsequent updates or upgrades after reaching 18.0. odoo/upgrade#6803
The Documents app now correctly copies shareable links when users select files from the list view. This prevents blank or missing links, making it easier for users to share documents reliably.
Original PR description
In list view, the "Copy links" [action](https://github.com/odoo/enterprise/blob/0c2b8ab5c0675485a8dbde3371e347f43250a66e/documents/static/src/views/search/documents_control_panel.xml#L42) was returning empty string (or undefined), since we haven't added the field `access_url` to the list view, so accessing it on the `record.data` [from JS](https://github.com/odoo/enterprise/blob/7a65d1e776ea486538cfc9762cb482fd71bf9dc1/documents/static/src/views/search/documents_control_panel.js#L262) returned `undefined`. Now, we add `access_url` field as a hidden field in the list view. opw-4309365
This fix ensures projects linked to shared documents are visible to portal users when needed. It keeps document access working as expected after related access rules changed, preventing failures for external users or automated checks.
Original PR description
Before this commit, the test fails due to the changes made in community to avoid having an access token if the project visibility is private. This commit makes sure the project visibility is `portal` to be able to set an access token as before. opw-4104804 task-4354145
The document deletion test tour has been adjusted to avoid timing-related failures caused by an error dialog appearing during automated checks. This helps keep validation runs more stable and faster, reducing false alarms for teams relying on test results.
Original PR description
In this commit, we fix the tour documents_delete_tours in which there is an error message that said: " Record does not exist or has been deleted. " As there is a modal in DOM, the next step could not be passed (depends on time the modal appears).
4 changes
Resolved issues and error corrections
This update prevents the creation of quality checks when inventory is marked as 'Scrapped' within Odoo. Previously, a quality check was automatically generated after a 'Scrap' action, which was an unnecessary step. This change streamlines the process and ensures accurate inventory tracking.
Original PR description
Steps to reproduce the bug: - Create a storable product “P1.” - Set up a quality point: - Control Per: By operation - Operation: Receipts - Product: P1 - Create a receipt for two units of P1. - Mark the receipt as "To Do." - Click on "Quality Check" → Fail. - Click on action → Scrap: - Scrap 1 unit of P1. - Confirm. Problem: A quality check is created for the scrapped move. This should not happen. opw-4345679
This update resolves a technical error that prevented users from successfully splitting documents when scheduling activities within the Documents module. The fix ensures that document IDs are correctly included, allowing the splitting functionality to work as intended. This improves the reliability of document management workflows.
Original PR description
useEffect hook on pdf_manager generates file urls from documents ids, before this commit documents comming from activity view didn't have id key set. Reproduce --- - install document - open documents activity view, schedule an activity with a document (that is possible to split) - attempt to split the document -> Traceback opw-4163726
This update resolves an issue where deleting all stages from a helpdesk ticket kanban view resulted in a blank screen. The fix ensures that the correct data is displayed after stage deletion, improving the user experience. The problem stemmed from a validation oversight in the system.
Original PR description
Steps: - Create a new helpdesk team. - Open tickets of that team. - Delete all ticket stages Issue: - If all the stages are deleted then the blank screen appears instead of shadow data. Cause: - Only `helpdesk.ticket` was being validated, but `helpdesk.stage.delete.wizard` was not included in the check. Fix: - The issue has been fixed by replacing active_model with default_team_id. task-4290529
This update corrects a technical issue that caused a traceback error when users interacted with the bank reconciliation feature in Odoo Enterprise. The fix ensures that the system correctly handles user selections, preventing errors and improving the overall stability of the accounting process. This resolves a minor disruption for users.
Original PR description
Fixing a traceback when selecting text, because the t-on-click was triggered but the target had no attribute. task: 4260301 Forward-Port-Of: odoo/enterprise#74509