Bug #2048
closed
right problems
100%
Description
*setting group rights has no effect on rights of the members of that group
*setting rights on e.g. 5 objects in my repo has no effect at all on each separate object
*setting rights on one particular object (S V U) does not seem to have an effect either: the selected user does not see the object in his repo's shared objects
Updated by Sven Vanpoucke over 12 years ago
This is a problem with the way how shared objects are retrieved. Due to performance reasons we can now only retrieve the locations on which a user has direct right (not through parents, not through groups) because otherwise we would need to retrieve each content object and check for rights. I don't know a direct solution for this and hope somebody could help me for this
Updated by Sven Vanpoucke over 12 years ago
- Status changed from New to Needs testing
- Assignee set to Sven Vanpoucke
- % Done changed from 0 to 100
Changed the entire rights system in the repository to improve the performance and fix these bugs
Updated by Ludwig Theunis over 12 years ago
- Status changed from Needs testing to Assigned
De object's are shared through a group are now visible for the groupmembers.
That is the objects are in the map shared with me in the repository.
But like issue #2070 clicking the visible objects icon as students result in a jump to the students repository root.
Like in #2070 it is not possible to really view the object. The name's of the visible, shared objects are also not a link. Only the documents icon is click-able.
Updated by Stefaan Vanbillemont over 12 years ago
- Target version changed from 18 to 21
Updated by Stefaan Vanbillemont about 12 years ago
- Project changed from Chamilo LCMS Connect to Repository
- Category deleted (
4)
Updated by Stefaan Vanbillemont about 12 years ago
- Target version changed from 21 to 2.1.0
Updated by a b