Opened 18 years ago
Closed 18 years ago
#280 closed defect (invalid)
Shared item doesn't appear in the list, though the item is shared to the user.
| Reported by: | Martin Svensson | Owned by: | Martin Svensson |
|---|---|---|---|
| Priority: | major | Milestone: | BASE 2.0 |
| Component: | web | Version: | |
| Keywords: | Cc: |
Description
Logged in as Root(Administrator)
eg. An item is shared to 'Everyone' and to one other group, both with Read and Use permission. When the permissions for Everyone stays unchanged and the other group gets write permissions the shared item disappear from the list even if 'Share to me' is selected.
Similar problem seems to be eg. when an item is shared to the logged in user.
Change History (2)
comment:1 by , 18 years ago
| Owner: | changed from to |
|---|
comment:2 by , 18 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Short answer: Use the menu: File -> Reload permissions
Long answer: For performance reasons the permissions for a user are loaded when the user logs in. Changes to the permissions for an item doesn't show up until the permissions are reloaded. This can be done manyally by the File -> Reload permissions menu. It will also happen automatically about every ten minutes.
Internally the permissions for an item are stored in an access control list (ACL). The ACL is simply a list of users, groups and projects together with their permissions for the item. Each ACL has a unique ID. When a user logs in the ID:s of all ACL:s where the user appers are loaded into memory. This makes it easy to list items that are shared to a user since we just have to say: give my all items which have an ACL with an ID in this list of ID:s.
Now, when the permissions for an item is changed the core may have to create a new ACL for that item. Obviously the new ACL gets a new ID which of course isn't in the list preloaded into memory. Therefor the item disappears from the list until the permissions are reloaded.