<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>There was a bug in the current jsDAV package we use for the NPM installation. I just released a fix and updated the NPM install sources.</div><div><br></div><div>The easiest way to get the most recent version is to stop your server, delete the node_modules directory and start the server again (the modules Lively depends on will be downloaded to the node_modules folder again - including the patch).</div><div><br></div><div>Let me know if it did not work (I just tried that and it fixed it for me).</div><div><br></div><div>----------------------------------------</div><div><br></div><div>For everyone interested in where the place for browsing directories is, here is the solution: LivelyKernel --references-> life_star --references-> lively-davfs --references-> jsDAV.</div><div>Yet, this jsDAV is not the regular one but <a href="https://github.com/LivelyKernel/jsDAV/tree/windows-compat">https://github.com/LivelyKernel/jsDAV/tree/windows-compat</a> (referenced as <a href="https://github.com/LivelyKernel/jsDAV/releases/tag/windows-compat">https://github.com/LivelyKernel/jsDAV/releases/tag/windows-compat</a> respectively the lk-master branch in lively-davfs/package.json).</div><div>This jsDAV version differs in a few things (<a href="https://github.com/LivelyKernel/jsDAV/compare/lk-master">https://github.com/LivelyKernel/jsDAV/compare/lk-master</a>) but especially in which jsDAV plugins get loaded.</div><div><br></div><div><div>----------------------------------------</div></div><div><br></div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Marko</div><div><br></div><div><br></div><br><div><div>On 04 Mar 2014, at 15:05, Sean DeNigris <<a href="mailto:sean@clipperadams.com">sean@clipperadams.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Mar 4, 2014, at 9:03 AM, Lincke, Jens <<a href="mailto:Jens.Lincke@hpi.uni-potsdam.de">Jens.Lincke@hpi.uni-potsdam.de</a>> wrote:<div><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Did you file a bug report for this on <a href="https://github.com/LivelyKernel/LivelyKernel/">https://github.com/LivelyKernel/LivelyKernel/</a> ?
</div></blockquote></div>I will if you think it’s appropriate, but from my POV I don’t know if it’s a bug. Maybe it’s possible already? Maybe it’s a node configuration issue?</div>_______________________________________________<br>lively-kernel mailing list<br><a href="mailto:lively-kernel@hpi.uni-potsdam.de">lively-kernel@hpi.uni-potsdam.de</a><br>http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel<br></blockquote></div><br></body></html>