trashbin not saved when files_trashbin not whitelisted

[phil-davis]

1. set the guests whitelist so that files_trashbin is not in the whitelist
2. user Alice creates folder trashbin-test and shares it with full access with a new guest [email protected]
3. user Alice creates file trashbin-test/file.txt
4. Guest [email protected] logs in and browses into folder trashbin-test
5. The guest deletes file.txt
6. user Alice views the trashbin

file.txt is not in the trashbin of Alice.

a) The content that Alice entered in file.txt has been deleted by the guest user, but is not available in the trashbin of Alice. Alice has "lost" that content.

(a) seems to be "not a good thing" - Alice loses data, and may quite reasonably expect that her data will be available in the trashbin.

If Alice deletes the file herself, then it does get put in the trashbin. So Alice might be quite confused about why she completely lost her file when she shared with a guest.

[phil-davis]

I think that the whitelist feature is intended to be used so that guests do not see some functionality. In this case (files_trashbin) the guest user should not see the trashbin (Deleted Files) on the classic webUI, and should not be able to use the API to query or restore from the trashbin.

But I think that when the guest deletes the file, the file should still be saved to the trashbin of Alice by the server - so that Alice (a real user) can have that available to her.

@pmaier1 what is the requirement?