fix: allow renaming files with just update permissions#57374
fix: allow renaming files with just update permissions#57374icewind1991 merged 4 commits intomasterfrom
Conversation
|
/compile |
|
(I'll rebase etc once reviewed) |
mgallien
left a comment
There was a problem hiding this comment.
tested with the desktop client and works fine
0f7b6d9 to
de3587d
Compare
|
@icewind1991 will this change be backported to stable branches ? |
de3587d to
8a6bf8a
Compare
mgallien
left a comment
There was a problem hiding this comment.
wrong test with only partial patch applied
I can confirm that this is working fine when applied on 30.0.11
4118102 to
ed3f042
Compare
|
/compile |
susnux
left a comment
There was a problem hiding this comment.
Makes sense but would it not make more sense to directly expose the permission in the backend?
| Boolean(node.permissions & Permission.DELETE) | ||
| && Boolean(parentPermissions & Permission.CREATE) |
There was a problem hiding this comment.
Would it not better to move the logic to the backend?
server/lib/public/Files/DavUtil.php
Line 36 in c826288
There was a problem hiding this comment.
Added the proper rename logic to the dav permissions.
But the permissions on the js side there is the numeric permissions mask (instead of the string flags), which doesn't distinguish the permissions.
Solving this would need changes in @nextcloud/files I think
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
069ced4 to
cdf9368
Compare
|
/compile |
c6e04cc to
13934cf
Compare
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
13934cf to
8f7b0b4
Compare
|
/backport to stable33 |
|
/backport to stable32 |
|
This breaks the existing usage of App will work fine with upgrading in patch level breaks the code. |
Only moving to another folder needs the delete+create permissions, for moving in the same folder just update is enough.
TODO: