Skip to content
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

WebDAV create and move broken inside shared folders #91

Closed
MTRichards opened this issue Oct 25, 2012 · 9 comments
Closed

WebDAV create and move broken inside shared folders #91

MTRichards opened this issue Oct 25, 2012 · 9 comments
Assignees
Milestone

Comments

@MTRichards
Copy link
Contributor

With a WebDAV client, when trying to create a folder or move a file in a directory that is shared from another user, ownCloud responds with 405 Method Not Allowed. All permissions are granted to the users that have access to the shared folder, but none of them can create folders or move files that are located in the shared folder. However, it is possible to copy a file from one folder to another, and then manually delete one of them afterwards. Sort of like a "manual" move operation. But since we try to avoid manual labor as much as possible, it would be nice if the move operation could be fixed :-)

These things work perfectly fine when you're working on your own folders. It's just the shared ones that are problematic.

@ghost ghost assigned MTGap Oct 28, 2012
@feinom
Copy link

feinom commented Oct 29, 2012

The same is true when trying to rename an existing file. It works on your own personal files, but fails when trying to rename a shared file/folder.

@Jasperado
Copy link

The same problem occurs when using the sync client (as described in #80).

This is an absolute blocker for our environment. Is it possible to get any estimation on when this issue might be addressed?

@MaximilianA
Copy link

+1 - this completely blocks the usage for us. So a ETA for the fix would be highly appreciated!

@directhex
Copy link

I can confirm that 3d13c9d appears to fix the problem

blizzz added a commit that referenced this issue Nov 6, 2012
Return empty array if file does not exist inside Shared folder, fixes issue #91
@MTGap
Copy link
Contributor

MTGap commented Nov 6, 2012

Cherry picking the commit into a new branch doesn't seem to work... Is there an easy way to do this backporting. This QA process requires too much time on my side if I need to do two different branches and pull requests. Any tips?

@Jasperado
Copy link

Manually adjusting the files.php in our production environment (clone of branch stable45) fixed it.It also fixed issue #80.
Thx btw.

@anamba
Copy link

anamba commented Nov 6, 2012

Same result as Jasperado, manually adding the $info = array() and the if block fixes these two issues for me.

With that resolved, I've now run into a different issue, but it appears to be unrelated (an OmniOutliner .oo3 file/bundle refuses to sync, although other bundles, and even other .oo3 files are fine).

@anamba
Copy link

anamba commented Nov 6, 2012

Never mind... it probably was related, as it was among the files I was trying to sync before resolving this issue. If I simply rename the file it syncs properly.

@DeepDiver1975
Copy link
Member

@MTGap It's not the CodeReview process itself which requires too much time but maintaining multiple releases is time consuming - but most of us will agree with me that that's a pure fact.
Sometimes it requires totally different patches to fix the same issue in different releases. But that's the way it is.
Yes - it's time consuming!

Enough on general talking:
I think you need to branch stable45, apply the patch manually (copy'n'paste) and push the merge request.

Take care!

@MTGap MTGap closed this as completed Nov 10, 2012
aditmeno pushed a commit to aditmeno/Aeolus that referenced this issue Apr 2, 2015
kill phpdocx, phpexcel and it's dependencies
@lock lock bot locked as resolved and limited conversation to collaborators Aug 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants