-
Notifications
You must be signed in to change notification settings - Fork 196
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
cannot move/rename an accepted shared resource outside of shares folder #2141
Comments
The problem is not with moving outside but move in general IMO |
also Related #2146 |
@dpakach renaming the shared file inside the shared folder is possible if only the sharee has edit permission. |
update:
|
This is expected behavior in oCIS (difference to how oC 10 handles the case). Please adjust the tests and remove from expected failures. |
Some of the test adjustments may have already been done. @dpakach please get someone to have a look - I remember that we recently looked at this related to other issues/discussions. |
Tests have been adjusted/skipped as appropriate. The defined-correct behavior on oCIS is that received shares are "jailed" inside the "Shares" folder and cannot be moved outside the "Shares" folder. Closing this issue. |
Describe the bug
A clear and concise description of what the bug is.
Steps to reproduce
Steps to reproduce the behavior:
uu1
anduu2
lorem.txt
withuu2
usinguu1
with edit permissionuu2
/Shares/lorem.txt
to/Shares/lorem-renamed.txt
/Shares/lorem-renamed.txt
to/lorem.txt
Expected behavior
FIles move should be successful with HTTP status
201
Actual behavior
MOVE request fails with status

400
and no contentSetup
Additional context
Relates issue is covered in test here
The text was updated successfully, but these errors were encountered: