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.
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). Let me know if it did not work (I just tried that and it fixed it for me). ---------------------------------------- For everyone interested in where the place for browsing directories is, here is the solution: LivelyKernel --references-> life_star --references-> lively-davfs --references-> jsDAV. Yet, this jsDAV is not the regular one but https://github.com/LivelyKernel/jsDAV/tree/windows-compat (referenced as https://github.com/LivelyKernel/jsDAV/releases/tag/windows-compat respectively the lk-master branch in lively-davfs/package.json). This jsDAV version differs in a few things (https://github.com/LivelyKernel/jsDAV/compare/lk-master) but especially in which jsDAV plugins get loaded. ---------------------------------------- - Marko On 04 Mar 2014, at 15:05, Sean DeNigris <s...@clipperadams.com> wrote: > On Mar 4, 2014, at 9:03 AM, Lincke, Jens <jens.lin...@hpi.uni-potsdam.de> > wrote: >> Did you file a bug report for this on >> https://github.com/LivelyKernel/LivelyKernel/ ? > 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? > _______________________________________________ > lively-kernel mailing list > lively-kernel@hpi.uni-potsdam.de > http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
_______________________________________________ lively-kernel mailing list lively-kernel@hpi.uni-potsdam.de http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
