-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
DAV permissions for read only single file shares indicate updatable #53041
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
Comments
One step further it actually seems like server/lib/private/Files/View.php Lines 1614 to 1616 in 01db539
For WebDAV there are and we have a similar logic in server/lib/public/Files/DavUtil.php Lines 59 to 61 in dae7c15
|
Ok so it seems we just loose the difference between move, rename and update permissions that the webdav response has in https://github.com/nextcloud-libraries/nextcloud-files/blob/main/lib/dav/dav.ts#L173C14-L202 @skjnldsv @susnux I think that is something we should handle in Edit: use case and catched when trying to hide a file action for files that user can not edit: https://github.com/nextcloud/files_lock/pull/683/files#diff-a09b7f67f5f992f7ef9d9299f6fac774fb218572c9c2960eb2c30293067a8843R25 |
So needs to be updatable only:
if a file has 'NV' then we can only rename or move it, maybe a new permission here. |
I'm not sure what other checks are using the updatable permission as well. Also for an incoming single file share it could be read only (1) as storage permission but the share itself would still be Currently I see no way around separate options to check if the file is renamable/movable |
This seems like a bug that i noticed when trying to check for the permissions using
@nextcloud/files
where it turned out my file action did not hide on read only shares.Steps to reproduce
<oc:permissions>SGDNV</oc:permissions>
indicating that the file can be updatedAdditional context
server/lib/public/Files/DavUtil.php
Line 36 in dae7c15
server/lib/private/Files/View.php
Lines 1482 to 1650 in 01db539
The text was updated successfully, but these errors were encountered: