-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
User cannot move shared file to shared folder #6707
Comments
Please upgrade to 12.0.3. It should be fixed there. |
We pulled 12.0.3, tried again and didn't work. There is another error that happens when an user tries to move a file from a shared folder A to another shared folder B. I've tried to move this file and received an error message. |
Tested this last error reported by me in the last comment, in nextcloud 13, the error did not happen. However, the error in this issue, reported by @dtygel , happens in nextcloud 13 (master) |
Aaah I missunderstood the problem. Moving a share into a share is not supported. |
OK @rullzer . |
The owner of files can do what they want with files. Like if you have
If the owner wants to move Bar into foo.
And the owner can share The reason we don't allow moving shares into shares is twofold:
|
Hi @rullzer . That is a good explanation. Besides that, I would like to report a bug, (maybe in other issue?) because when we move a mount point to inside another, it fails silently. The error in lib/private/Files/View.php:1729 does not happen because of a storage wrapper. In my case the Files_Trashbin/Storage (which is a wrapper) is a instance of OCP\Files\IHomeStorage . This error should happen when I move one SharedStorage to inside another. For the user to whom the file/folder is being shared, the operation seems to have been done perfectly, however when s/he reloads the page, the moved file is in the same place. Steps to reproduce: Tested in nextcloud 12 and 13 (master). |
When a share is moved inside another, will check if both shares have equivalence in sharing types, permissions and sharing targets. If they have, will remove the sharing of the first and move it inside the second. This changes a policy in nextcloud and I don't know if this will be accepted. nextcloud#6707 Signed-off-by: Vinicius Cubas Brand <viniciuscb@gmail.com>
When a share is moved inside another, will check if both shares have equivalence in sharing types, permissions and sharing targets. If they have, will remove the sharing of the first and move it inside the second. This changes a policy in nextcloud and I don't know if this will be accepted. nextcloud#6707 Signed-off-by: Vinicius Cubas Brand <viniciuscb@gmail.com>
This problem persists in 15, I have fedeated share from external NC, and I can move it only to folders I am not sharing at all. |
can not move files or directory |
Neverthless !!! the files and directory have been moved to the other Server |
FYI owncloud is the old directory from which I used to switch to nextcloud without renaming the directory [webdav] Fatal: Sabre\DAV\Exception\ServiceUnavailable: at <>
COPY /owncloud/remote.php/dav/files/g/Fam/F |
the Server log says "Login failed...." |
Now I can not login any more on both servers... Will probably have to wait some hours - |
The problem seems to be "Service not available" because of "too many logins" or something else.. |
I think it's the problem of federation shares described in |
workaround for some case if you just want to move very big directories without intention to create federation shares of this folders!!!
|
Steps to reproduce
Expected behaviour
File FI should be succesfully moved to folder FO, since the folder is also shared among both users.
Actual behaviour
In user's B view, it seems that everything worked fine. There is no warning, no error message, nothing. But when user B reloads the page, she sees that moving the file didn't work.
In the other way round, if User B had uploaded a file directly into folder FO, and user A tried to move this file out of this folder, the file will disappear to User B, who uploaded the file, definitely, and User A will have this file in his root folder, not shared. This is the expected behaviour in this direction, but the other way round it's not working as expected.
Server configuration
Nexclout in branch master
Operating system:
Ubuntu 16.04
Web server:
Apache
Database:
MySQL
PHP version:
7.2
Nextcloud version: (see Nextcloud admin page)
12.0.1
Updated from an older Nextcloud/ownCloud or fresh install:
Fresh install
Where did you install Nextcloud from:
Github, branch master
Nextcloud log (data/nextcloud.log)
No error in log when doing this operation.
Browser log
No errors in javascript console nor in network.
The text was updated successfully, but these errors were encountered: