#266
- Created on2011-04-19 15:39
- Reported by
- Worked hours2.0 hours
- StatusTest
- PriorityNormal (3)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
Permission change notifications.
It turns out that changing the permissions is causing ALL affected items (e.g. the tree) to generate email notifications. Only the top level item should be affects; add an extra parameter flag to the applicable calls to turn off the event, so that when called recursively, only the first call triggers the event.
Leave a comment
on 2011-04-19 22:39 *
By joseph.gay
Status changed from Accepted to Test
Work remaining changed from 3.0 to 0.0
Commits f2430e2f and d5211fe9 should address the bulk of this issue.
The culprit appears to have been the Public Folder event handler that fixes up Public File/Folder permissions on a ViewableTreeChange. It calls the add/removeGroup/UserPermission core API methods for each public item it needs to fix. The changes add a flag so that the Public Folder code can turn off notifications for permissions changes made when handling a ViewableTreeChange.
__
The culprit appears to have been the Public Folder event handler that fixes up Public File/Folder permissions on a ViewableTreeChange. It calls the add/removeGroup/UserPermission core API methods for each public item it needs to fix. The changes add a flag so that the Public Folder code can turn off notifications for permissions changes made when handling a ViewableTreeChange.
__