-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 Locking (WebDrive) not working #2166
Comments
Could you please give more details, best using this template? Thanks! https://raw.github.com/owncloud/core/master/issue_template.md |
@bartv2 Do you know how and if we support the locking here at all? |
Bboule, Someone would be happy to assist you if you visit our online helpdesk at www.srthelpdesk.com (I work for the publisher of this application). Once you are there, simply click "Submit a Ticket" and please describe your problem in detail. If you could also include a debug log, that would be appreciated. Someone will respond to you as soon as possible. Thanks! |
Hey guys sorry I got pulled away from this, @bartv2 let me try running the litmus test suite and report back |
@bboule Any news on that? |
Guys, I am going to deal with this today, I will keep you posted, the more I dig at this the more I think this is a client specific issue, but my plan is to run the litmus test assuming it passes for the lock, I will go back to the WebDav client developer and present this to them and ask for assistance. I will close this for now and re-open if needed. Apologies for the delay on this one!! I will also test this against OC 5!! |
Hi, I'm also having problems with locking: In linux, I open kate, open a txt file via web dav in computer 1 and computer 2, make changes, I've just run the litmus tests. -> running `basic':
note: "?" on the error is an recognizable character |
Version ownCloud 5.0.4 (sorry) |
Using Ubuntu 12.04 with MySQL and Apache accessing files via webdav client (WebDrive) file locking is not working properly. ownCloud doesn't report the correct lock tokens during PROP requests.
The text was updated successfully, but these errors were encountered: