-
-
Couldn't load subscription status.
- Fork 4.6k
fix: Use default share folder of the user on share accept #51602
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: Use default share folder of the user on share accept #51602
Conversation
5140ae4 to
51e3d97
Compare
|
/backport to stable28 |
|
/backport! to stable28 |
|
@susnux @icewind1991 @artonge |
|
I believe Probably makes sense to add a |
51e3d97 to
373969b
Compare
That would be cleaner but would make backporting hard, so I would say for now a simple solution is needed. According to the type list above @icewind1991 , I believe this PR can be reviewed and merged as-is, as the only known type handled by |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
…eter Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
373969b to
7070ba4
Compare
|
/backport to stable31 |
|
/backport to stable30 |
|
/backport to stable29 |
Summary
When sharing to a group, it was not respecting the default share folder of each user.
The code was trying to set the target on the group share on creation, while it needs to be done on acceptance for each user, as each user may have a different configuration.
I’m wondering if we should not do the same for user shares as well and only set target when accepting, and also whether it’s expected that we set target for all types of shares. What’s the target for on link shares or share by mail? But maybe it’s needed for federated shares or whatever so I did not remove that.
Checklist