You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would result in following error (here for idreport=20): ScheduledReportsAPI.sendReport_20,ERROR: U kunt deze bron niet verwijderen omdat 'view' toegang is vereist
Goal of this ticket is to make scheduled task work, even though reports don't have necessary permissions.
More info: there are two solutions to this:
when user loses access to a website, we could delete the reports for this user and website,
or we could skip trying to send reports when a user does not have permission.
I think skipping reports is better solution, because in case the Super User deletes permission from user by mistake, then restores the permission, then user should still have his scheduled reports working.
The text was updated successfully, but these errors were encountered:
mattab
changed the title
When an admin removes a user\' access to a website, scheduled reports for this
When an admin removes a user's access to a website, sending scheduled reports may fail
Aug 7, 2014
…he user has no longer access to this site. To make sure it works I added a usersManagerApiTest to verify whether an event is triggered in this case, and added a ScheduledReportsTest to make sure it listens to this event and that it only removes sites that belongs to the user/sites.
Reproduce:
core:archive
It would result in following error (here for idreport=20):
ScheduledReportsAPI.sendReport_20,ERROR: U kunt deze bron niet verwijderen omdat 'view' toegang is vereist
Goal of this ticket is to make scheduled task work, even though reports don't have necessary permissions.
More info: there are two solutions to this:
I think skipping reports is better solution, because in case the Super User deletes permission from user by mistake, then restores the permission, then user should still have his scheduled reports working.
The text was updated successfully, but these errors were encountered: