Daily updates from Odoo
Saturday, January 11, 2025
3 changes
Resolved issues and error corrections
Users can now mention internal colleagues in a discussion channel even if those colleagues are not channel members, as long as they have access to the channel. This makes collaboration smoother and ensures mentioned users are notified through their inbox or email.
Original PR description
Current behavior before PR: In channel it was not possible to mention internal users which are non-members of channel. Desired behavior after PR is merged: now it is possible to mention internal users who has access to the channel task-4100364 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes several issues with document shortcuts, especially when items are in the trash or point to archived folders. Users can now delete trashed shortcuts, open valid original documents from shortcut details, and access permitted trashed documents by direct link without errors or inconsistent behavior.
Original PR description
Issue 1: Reproduce: 1. Create a shortcut for a folder. 2. Move the shortcut to the trash. 3. Go to the trash and try deleting the shortcut. 4. You get a 'Missing Record' message. Issue 2: While in the trash you cannot open folders, if you had a non-archived shortcut to an archived folder you were able to view its (archived) target content there. Issue 3: Reproduce: 1. Create a shortcut in your drive for a document in "Share with me" 2. Click on the shortcut and from the details panel click on the button allowing to jump to the original document (target or source) 3. There is your traceback In fact, the same applies for documents in "My Drive" and "Company" Issue 4: Reproduce: 1. Select a document you are allowed to "Move to trash" 2. Copy its url 3. Send it to the trash 4. Go to the URL 5. You are not getting to the record even though you are allowed to access it. Task-4433373
Documents linked to a company that a user has disabled are now correctly hidden, even when the folder itself is shared broadly. This prevents users from seeing documents outside their currently enabled company context and keeps multi-company access rules consistent.
Original PR description
Bug === 1. create a folder without company, and access_via_link='view' 2. create a document with a company A, and access_via_link_hidden=False 3. create a member in the folder 4. log-in using that member and disable the company in the interface => The document should be hidden since the company is not enabled, but it still visible Task-4463854