mirror of
https://github.com/nextcloud/desktop.git
synced 2024-11-27 09:30:13 +03:00
Repair the canAddToDir logic
This could only work at the root of the sync folder where the record for the parent folder would be invalid. Otherwise the negation would be wrong... assuming you can add a file only if the permission is not there. Signed-off-by: Kevin Ottens <kevin.ottens@nextcloud.com>
This commit is contained in:
parent
00e901f5a7
commit
26d62a9712
1 changed files with 3 additions and 2 deletions
|
@ -891,8 +891,9 @@ void SocketApi::command_GET_MENU_ITEMS(const QString &argument, OCC::SocketListe
|
|||
const auto parentDir = fileData.parentFolder();
|
||||
const auto parentRecord = parentDir.journalRecord();
|
||||
const bool canAddToDir =
|
||||
(fileInfo.isFile() && !parentRecord._remotePerm.hasPermission(RemotePermissions::CanAddFile))
|
||||
|| (fileInfo.isDir() && !parentRecord._remotePerm.hasPermission(RemotePermissions::CanAddSubDirectories));
|
||||
!parentRecord.isValid() // We're likely at the root of the sync folder, got to assume we can add there
|
||||
|| (fileInfo.isFile() && parentRecord._remotePerm.hasPermission(RemotePermissions::CanAddFile))
|
||||
|| (fileInfo.isDir() && parentRecord._remotePerm.hasPermission(RemotePermissions::CanAddSubDirectories));
|
||||
const bool canChangeFile =
|
||||
!isOnTheServer
|
||||
|| (record._remotePerm.hasPermission(RemotePermissions::CanDelete)
|
||||
|
|
Loading…
Reference in a new issue