When I asked for Disabling the pad deletion token UI when allowPadDeletionByAllUsers is true in #7926, I didn't realize that allowPadDeletionByAllUsers really does what it says..: Pads can be deleted by any user.
So now (in v3.3.2) I have the choice between showing the pad deletion token OR allowing all users to delete a pad, even if they are not the creator - which is a problem
What I actually want is:
- a) no "pad deletion token" UI, or at least a way to disable the default display of the token (because it confuses some user groups).
- a1) for those user groups, in my point of view it would actually be fine to have the token functionality active, if the token-popup would be supressed, but the token accessible in the settings. in this way, users who understand the option can find and use it, but others wouldn't have to bother
AND at the same time
- b) disallow Pads to be deleted by others than the creator (to prevent or data loss by clicking "delete" on the wrong pad, or prevent students trolling their teachers..). I am fine with the way it worked until some updates ago: only in the creating browser session, the pad could be deleted
- b1) additionally, it would be great to
- hide the "delete" button if the session is not the creators session
- have an instance settings.json option to disable the "delete pad" completely
If you don't like a1) from UX/other use cases' point of view, we would need a settings.json option to disable the "delete pad with token" functionality WITHOUT allowPadDeletionByAllUsers
b1) is a nice-to-have, not a solution to my problem
When I asked for Disabling the pad deletion token UI when allowPadDeletionByAllUsers is true in #7926, I didn't realize that
allowPadDeletionByAllUsersreally does what it says..: Pads can be deleted by any user.So now (in v3.3.2) I have the choice between showing the pad deletion token OR allowing all users to delete a pad, even if they are not the creator - which is a problem
What I actually want is:
AND at the same time
If you don't like a1) from UX/other use cases' point of view, we would need a settings.json option to disable the "delete pad with token" functionality WITHOUT allowPadDeletionByAllUsers
b1) is a nice-to-have, not a solution to my problem