Issue 13069

Summary: File locking causes problems with webDAV
Product: ucb Reporter: oliverk <oliver>
Component: codeAssignee: oliverk <oliver>
Status: CLOSED IRREPRODUCIBLE QA Contact: issues@ucb <issues>
Severity: Trivial    
Priority: P3 CC: issues
Version: OOo 1.1 Beta   
Target Milestone: ---   
Hardware: Other   
OS: Linux, all   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---

Description oliverk 2003-04-05 18:04:08 UTC
When opening a previously saved file over webDAV, OO opens it as read-only, I assume due to 
the file-locking function added in 1.1 Beta - this wasn't a problem with earlier versions. 
 
This is using mount.davfs on Linux rather than OO's built in webDAV which I can't get to work. 
We have also found this problem on Windows XP using it's built in webDAV but only intermittently. 
 
My request is that there be a switch in the UI (tools->options perhaps) that could be used to 
disable file locking if necessary.
Comment 1 oliverk 2003-04-05 18:08:38 UTC
Ah I've just found the 'Edit File' button on the toolbar that lets you edit and save the 
'locked' file, so this isn't such a major problem any more. 
Comment 2 matthias.huetsch 2003-04-07 20:32:01 UTC
Hi Oliver,

The issue that you described has most probably nothing to do with
file locking. It is a general behaviour of OOo that files requiring
to be downloaded upon 'open' (and to be uploaded upon 'save') such as
files from 'ftp' / 'http' (WebDAV) servers, or otherwise can't be
locked for exclusive write access, are initialy opened as 'readonly'.

This behaviour is implemented in the 'framework' project, independent
from what the 'ucb' would do, and actually was designed to work like
this.

Whatever file you have, you can always press 'Edit File'. If all else
fails, OOo will ask whether you want to work on a copy of the original
file. But editing should always work.

Finally, and now that you have discovered the 'Edit File' button,
such that '...this isn't such a major problem anymore...', I'm going
to close this issue as 'works as designed' or such.

To proceed, you have different possibilities:

1) If you don't agree, you can always reopen this issue, for whatever
   reason.

2) If you think the current behaviour / design should be changed, you
   can reassign this issue to the 'framework' project (as explained
   above.

3) If you think there's still something wrong with OOo's WebDAV client
   implementation, you can reassign this issue to 'kso@openoffice.org'
   who takes care of the UCB's WebDAV client in OOo.

Hope that helps,
Matthias
Comment 3 matthias.huetsch 2003-04-07 20:38:29 UTC
Resolving as 'works for me'...
Comment 4 matthias.huetsch 2003-04-07 20:38:54 UTC
Closing...