-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
unfortunate notification wording when removing share #9180
Copy link
Copy link
Closed
Labels
1. to developAccepted and waiting to be taken care ofAccepted and waiting to be taken care ofdesignDesign, UI, UX, etc.Design, UI, UX, etc.enhancementgood first issueSmall tasks with clear documentation about how and in which place you need to fix things in.Small tasks with clear documentation about how and in which place you need to fix things in.
Milestone
Metadata
Metadata
Assignees
Labels
1. to developAccepted and waiting to be taken care ofAccepted and waiting to be taken care ofdesignDesign, UI, UX, etc.Design, UI, UX, etc.enhancementgood first issueSmall tasks with clear documentation about how and in which place you need to fix things in.Small tasks with clear documentation about how and in which place you need to fix things in.
Type
Fields
Give feedbackNo fields configured for issues without a type.
On our Nextcloud installation, we have a share for all users, matching the name of the url
cloud.example.com. It contains all data about the installation and the finances for transparency purposes.While reordering the files, we removed everyone from that share following the logic from the code below, everybody got an email saying
Admin removed your from cloud.example.com:server/apps/files_sharing/lib/Activity/Providers/Users.php
Line 95 in da6c2c9
Many of our users thought their accounts have been deleted or deactivated.
An improvement in wording is desirable. Something like
{actor} removed you from the share named {file}. Preferably referencing the specific share entity (file or folder) to be more clear.I know all translations would need to updated as well (we had the problem in German), but I believe it's important to give the users more clarity about whats happening.