Saturday, January 11, 2025
5 changes · 18.0
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
This fixes how Odoo's web test system clears memory between test groups after a Chrome browser change made results inconsistent. It helps keep automated test runs stable and predictable, reducing false alarms in development workflows.
Original PR description
Since [1], we force the garbage collector to run between each hoot test suite. However, since chrome 124, this no longer seemed to produce the desirable effect. Indeed, memory graphs of the test suites were no longer predictable. The garbage collector seemed to work differently from a build to another, even with the same code. This is probably due to this change [2] in chrome, coming with version 124. Hopefully, the commit message gave us a hint on a way to fix our issue. [1] https://github.com/odoo/odoo/commit/a3ef39dae4a7cd6c96f14958744ac8d8bd2064c9 [2] https://chromium.googlesource.com/chromium/src/+/ae7269f134ede59c815b22c1fd042b26bab96b7a Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The export option for updating existing data now correctly hides read-only fields. This prevents users from including values that cannot be re-imported or updated, reducing confusion and failed data update workflows.
Original PR description
Issue ----- Read-only fields appear in the export menu when the "I want to update data (import-compatible export)" checkbox is active. Cause ----- The `readonly` key is missing from the field dictionnary leading to all fields being considered as not read-only. https://github.com/odoo/odoo/blob/a546e2e5a87c311bef054ca4a6909e63d70c91fd/addons/web/controllers/export.py#L389-L390 Issue from 2b87effeb461acddf327884dd72c00ee22a4c9aa since only some attributes of the fields are fetched. opw-4446090
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