-
Notifications
You must be signed in to change notification settings - Fork 671
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
Recipient cannot access shared files #7419
Comments
Probably relates to owncloud/core#35884 |
@HanaGemela Do you have a log file? Particularly the lines around "Received sharing permissions for" when user A shares the folder initially are interesting. The client is intended to discover the maximum possible permissions for sharing of an item and then create a user share with that. See |
I can't reproduce the problem. Spoke to @HanaGemela, she'll also try to reproduce and save logs. |
I cannot recreate either. The below is the error for the file not synced yesterday
The file is not present in Windows Explorer |
Reproduced. But I don't think I used webUI yesterday. But I run many tests so I can't be 100% sure
Actual result: One file (out of three shared ones) has access denied Logs shared |
@HanaGemela I tried reproducing, but it did work alright for me. Notable difference is that when I set up the group share with the webui by default all permissions are checked. What do you mean with "one out of three" - you only mention one file, test.txt.txt. |
I shared the whole folder I've uploaded on the server. It includes file.txt.txt and subfolder called Sub. Sub includes file1.txt.txt and file2.txt.txt
This can be set in Settings -> Admin -> Sharing -> Default user and group share permissions |
I still can't reproduce the problem. Now with several files in a subfolder of the shared folder, and the default share permissions disabled. |
Also, if this problem happens when you set up the share via the webui it's really unlikely to be a client issue. |
This situation could arrise when receiving a read-only share and the temporary rename failed for some reason. See #7419
Steps to reliably recreate:
|
This situation could arrise when receiving a read-only share and the temporary rename failed for some reason. See #7419
I've tested with file titled sample.txt, client 2.6.0rc1 (build 12411), macOS 10.14.6 |
Moved to 2.6.1 as it is not a blocker for 2.6.0 |
Looks like the file is either hidden, or still read-only. Could find out from the shell why it is gray? |
@ogoffart When the hidden files are visible, the new file is grey. When hidden files are hidden, the new file is normal black. |
@HanaGemela Could you open a new issue with the remaining things to improve? Then close here. |
Last remaining question moved to #7618 |
Windows 10
Client: 2.6.0daily20190820 (build 12286)
Server: 10.3.0 alpha, 10.2
Steps to recreate:
Actual result: Access to files denied
Expected result: Files are accessible
The text was updated successfully, but these errors were encountered: