To reproduce use the experimental OpenKM public WebDAV: 1) confirm you don't have the LO custom dialogs enabled; 2) with a browser login at: http://demo.openkm.com/OpenKM/login, choose whatever user+password you prefer from the list given there; user name and password will be used to access the server from LO. 3) load a test file of your choice into LO from your PC 4) select 'File > Save to Remote Server' from menu 5) add the new server to the list of available server using the 'Add service' button, with the following setup: Host: demo.openkm.com port: 80 label: your choice root: /OpenKM/webdav/ confirm and input user and password of point 1) 5) navigate to okm_personal/<user name> folder; 6) press the 'Create Folder' button; 7) a dialog to request the folder name is show, press OK; 8) the same dialog is presented again, navigate to the same parent folder using the browser connected as in 1) and press the refresh button in the OpenKM toolbar: no folder was created.
On pc Debian x86-64 with master sources updated today, I could reproduce this. Here is console log I noticed: warn:ucb.ucp.webdav:23406:1:ucb/source/ucp/webdav-neon/webdavcontent.cxx:3735: Content::getResourceType returned errors, DAV: 2, http error: 0
(In reply to Julien Nabet from comment #1) > warn:ucb.ucp.webdav:23406:1:ucb/source/ucp/webdav-neon/webdavcontent.cxx: > 3735: Content::getResourceType returned errors, DAV: 2, http error: 0 That DAV error means "User authentication failed on server", you can find it here: <http://opengrok.libreoffice.org/xref/core/ucb/source/ucp/webdav-neon/DAVException.hxx#114>. By looking at the debug log you see this line before the one you reported: info:ucb.ucp.webdav:24876:1:ucb/source/ucp/webdav-neon/webdavcontent.cxx:423: Content::execute: start: command: getPropertyValues, env: missing it tells you the xCommandEnvironment is missing, meaning the interaction handler needed for authentication is missing as well.
Giuseppe Castagno committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=4e8e637374f8dad5439da39bd0c4b8b0b7c13cde tdf#101766: Fix new folder creation in 'Save Remote Server' dialog. It will be available in 5.3.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Hello, Is this bug fixed? If so, could you please close it as RESOLVED FIXED?
Dear developer, This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assigned it back to yourself if you're still working on this.
(In reply to Julien Nabet from comment #1) > On pc Debian x86-64 with master sources updated today, I could reproduce > this. > > Here is console log I noticed: > warn:ucb.ucp.webdav:23406:1:ucb/source/ucp/webdav-neon/webdavcontent.cxx: > 3735: Content::getResourceType returned errors, DAV: 2, http error: 0 Hi Julien, Could you please check whether this bug is fixed?
It seems to hang after having filled the user and passwd. Save button is disabled, I can click "Cancel" and it indeed cancels but I can't see any directory. Here are the last traces on console: (pkix_CacheCert_Add: PKIX_PL_HashTable_Add for Certs skipped: entry existed (pkix_CacheCert_Add: PKIX_PL_HashTable_Add for Certs skipped: entry existed (pkix_CacheCert_Add: PKIX_PL_HashTable_Add for Certs skipped: entry existed (pkix_CacheCert_Add: PKIX_PL_HashTable_Add for Certs skipped: entry existed (pkix_CacheCert_Add: PKIX_PL_HashTable_Add for Certs skipped: entry existed
** 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 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 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: 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 Giuseppe Castagno (aka beppec56), 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
I can't reproduce this issue in bibisect-linux-5.3 master or newer 7.2, 7.3. The console message from comment 7 is also gone, although I saw it in bibisect-linux-5-3 oldest, where folder creation indeed did not work.