Re: [Components] Ez webdav + lighttpd: cadaver error when connecting: "Could not access /test/ (not WebDAV-enabled?): Could not parse response status line"

Hi Derick and Toby, Simply setting the data.timezone to "Europe/London" fixed it! Thankyou very much for the quick support. As for the tutorial, could I suggest that you add a few lines to mention this side affect? Also, I had to guess the redirect line in lighttpd.conf, so maybe it would be n

Re: [Components] Ez webdav + lighttpd: cadaver error when connecting: "Could not access /test/ (not WebDAV-enabled?): Could not parse response status line"

Hi, in addition to Dericks answer regarding date.timezone: On 06/03/2009 12:55 PM london...@hushmail.com wrote: > I have turned on the logging in php.ini, created testfile.txt, > changed index.php to take into account rewrite. > > I now get warnings in the browser relating to EZ components. Bu

Re: [Components] Ez webdav + lighttpd: cadaver error when connecting: "Could not access /test/ (not WebDAV-enabled?): Could not parse response status line"

On Wed, 3 Jun 2009, london...@hushmail.com wrote: > Ok, - done this, I now get the following warnings in browser when > accessing http://locahost/testfile.txt > > Strict Standards: DateTime::__construct() [function.DateTime--- > construct]: It is not safe to rely on the system's timezone > sett

Re: [Components] Ez webdav + lighttpd: cadaver error when connecting: "Could not access /test/ (not WebDAV-enabled?): Could not parse response status line"

Hi Toby, Thank you for the quick reply. I have turned on the logging in php.ini, created testfile.txt, changed index.php to take into account rewrite. I now get warnings in the browser relating to EZ components. But still the same result in cadaver. See below for details.. Regards On Wed, 0

Re: [Components] Question: Workflow: suspend on inputs/ prepopulated input nodes & joining variables

Gary Stocker schrieb: > We're making really good progress with our implementation of > ezcWorkflow, its proving to be really powerful and perfect for us, > thanks to all who've been involved with it :) You are welcome, glad to hear that you like the component. > We have an input node that define

[Components] Support on using/testing webdav

Hi List, it would be very helpful if there was an official ez webdav server (properly configured :-)) that anyone can use for testing his client configuration. getting a webdav configuration up and running is very time consuming if you dont know wether the problem is on server or client side

Re: [Components] Ez webdav + lighttpd: cadaver error when connecting: "Could not access /test/ (not WebDAV-enabled?): Could not parse response status line"

Hi, On 06/03/2009 09:48 AM london...@hushmail.com wrote: > However, I get the following error when connecting to the webdav > directory using the Cadaver webdav client: > > $ cadaver http://localhost/test > > Could not access /test/ (not WebDAV-enabled?): > Could not parse

[Components] Ez webdav + lighttpd: cadaver error when connecting: "Could not access /test/ (not WebDAV-enabled?): Could not parse response status line"

Hi, I am attempting to follow the EzComponents WebDav tutorial (http://ezcomponents.org/docs/tutorials/Webdav) to setup their webdav component on my local test Lighttpd server. However, I get the following error when connecting to the webdav directory using the Cadaver webdav client: