To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94354
User mav changed the following: What |Old value |New value ================================================================================ Status|UNCONFIRMED |RESOLVED -------------------------------------------------------------------------------- Resolution| |INVALID -------------------------------------------------------------------------------- Target milestone|OOo 3.0.1 |OOo 3.1 -------------------------------------------------------------------------------- ------- Additional comments from m...@openoffice.org Mon Jan 12 10:30:10 +0000 2009 ------- Lets see which problems was described here: 1) The main problem: the comment from submitter ( jska ) from "Sep 30 18:33:27 +0000 2008" explains that GMX client is used during the test to access the file, the client mounts webdav folder locally. As result the lock file can not be created because of settings on the webdav server. As I have written already this is definitely a problem of the GMX webdav server settings. 2) The Windows system file open dialogs can not open directly https://mediacenter.gmx.net. This is a problem of the system file dialog. It is also reproducible in older OOo versions ( OOo2.4 ) and has nothing to do with OOo implementation itself. It is system file dialog the OS is responsible for its implementation. 3) OOo file dialog can not open the URL ( https://mediacenter.gmx.net ). It can, and the user will even be asked for authentication. After that there is a message that there is nothing in "/" folder, FireFox browser shows exactly the same message. So it is again no problem of OOo. As result - this is an invalid bug since it has nothing to do with OOo. These problems are caused by third party implementations. Although there will be a workaround for the first problem caused by GMX webdav server settings in OOo3.1 as mba has mentioned. Based on the arguments above I am closing the issue as invalid, that does not mean that the discussion is closed. Please correct me if I have misunderstood/missed one of the mentioned scenarios. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org