-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(trash): Fix deleting items from public share with write access #3604
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💚 thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it makes sense. If an anonymous user deleted a file from a public share, then we should say so and not accuse the owner of the public share.
Maybe using a placeholder like "anonymous public user" would be better?
@kyteinsky Can you test the behavior when using |
When no user in session, use an empty string as deleted_by, which shows as "Unknown" in the UI. Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
b293363
to
574c909
Compare
maybe we can also change the term "Unknown" to "Anonymous Public User" like @artonge suggested? Or "Unknown" is fine too. |
/backport to stable31 |
/backport to stable30 |
/backport to stable29 |
The backport to # Switch to the target branch and update it
git checkout stable30
git pull origin stable30
# Create the new backport branch
git checkout -b backport/3604/stable30
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 574c909c
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/3604/stable30 Error: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
The backport to # Switch to the target branch and update it
git checkout stable29
git pull origin stable29
# Create the new backport branch
git checkout -b backport/3604/stable29
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 574c909c
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/3604/stable29 Error: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
I think the (new) fix still doesn't work! Steps to reproduce:
The file will still not be removed until the app "deleted files" is deactivated! |
This is specific to objectstore storage, and comes from #3481 |
When no user in session, default to owner.
Fix #3544 hopefully.