When I access to a document via webdav I can open, edit and save the file but the file it's not locked during editing. It seems 3.4.1 is supporting lock but it doesn't run. Here a webdav conversation 1-LibreOffice request Header PROPFIND <?xml version="1.0" encoding="utf-8"?> <propfind xmlns="DAV:"><prop> <resourcetype xmlns="DAV:"/> <IsReadOnly xmlns="http://ucb.openoffice.org/dav/props/"/> <getcontenttype xmlns="DAV:"/> <supportedlock xmlns="DAV:"/> </prop></propfind> 2-Server answer: <?xml version="1.0" encoding="utf-8" ?> <multistatus xmlns="DAV:"><response><href>/arkDocs//fs1/Applicazioni/ArkExample/Documenti/DOC000000051.odt</href> <propstat><prop><resourcetype/><IsReadOnly xmlns="http://ucb.openoffice.org/dav/props/">false</IsReadOnly> <getcontenttype>application/vnd.oasis.opendocument.text</getcontenttype> <supportedlock><lockentry><lockscope><exclusive/></lockscope><locktype><write/></locktype></lockentry><lockentry><lockscope><shared/></lockscope><locktype><write/></locktype></lockentry></supportedlock> </prop> <status>HTTP/1.1 200 OK</status> </propstat> </response> </multistatus> 3-LibreOffice request GET 4-Server answer file data.... Is it a bug?
see <https://issues.apache.org/ooo/show_bug.cgi?id=29152> "webDAV locking needs to be implemented"
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Setting to new, as this is a known lacking feature. Alex
And it won't be addressed any time soon in Apache OOo by the looks of it because they've just removed webdav support due to licensing restrictions of the neon code. Alex
Does this bug apply anymore? It seems to run contrary to what is described in bug 72157. Is locking over WebDAV implemented or not? Are these two bugs describing a different level of file locking? Just after some clarity for answering WebDAV-related questions on AskLO. Thanks.
Owen, bug 72157 isn't fully fixed, have a look at latest comments there.
(In reply to comment #0) > When I access to a document via webdav I can open, edit and save the file > but the file it's not locked during editing. (In reply to comment #6) > Owen, bug 72157 isn't fully fixed, have a look at latest comments there. Thanks. I can see that bug 82744 now indicates that the save action is unlocking the WebDAV-acquired file, but doesn't that make this report now an even more likely duplicate? I confess to not understanding WebDAV requirements at all. Some users seem to want to turn off all file locking (e.g., http://ask.libreoffice.org/en/question/36303/), while others insist on it (which I would think more sensible). At present, neither option seems workable.
please give an update of the current bug status with latest LibO 4.4.3.2 release
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Dear Davide Dozza, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Davide Dozza, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug