Hi Russel, I could not reproduce your problem with the latest nightly build.
Which version of SLIDE did you use? What exactly is your scenario? How did you set DAV:auto-version to DAV:checkout? Could is be misspelling of the property name (DAV:autoversion instead of DAV:auto-version)? Roughly, what I did is the following: - PUT /slide/files/a.xml - VERSION-CONTROL /slide/files/a.xml - PROPPATCH /slide/files/a.xml (DAV:auto-version = DAV:checkout VERSION-CONTROL creates a history at /slide/history/1 and a 1st version /slide/history/1/1.0. Due to DAV:auto-version = DAV:checkout-checkin, the PROPPATCH creates a 2nd version /slide/history/1/1.1. My scenario continues: - PUT /slide/files/a.xml - PROPFIND /slide/files/a.xml (requesting DAV:checked-out and DAV:checked-in) - PROPFIND /slide/history/1 (Depth: 1) Both PROPFINDs show me that the resource is checked-out and that no new version has been created. Regards, Peter > -----Original Message----- > From: Thamm, Russell [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 15, 2002 08:33 > To: Slide Users Mailing List > Subject: Problems wih DAV:autoversion = DAV:checkout > > > Hi, > > I have been playing with the DELTAV stuff in Slide. > > Everything seems to work pretty much as expected. But when I set > autoversion to checkout, Slide does not behave as I expect. > > According to my understanding, if I PUT a new copy of a checked-in > version-controlled > resource, the old copy should be checked out, the new copy > should overwrite > the > checked-out resource, but no checkin should occur and no new > version should > be created until I perform an explicit checkin. > > However, when I do this, Slide creates a new version, exactly as if > autoversion were set to checkout-checkin. > > Am I misunderstanding this? > > thanks > Russell Thamm > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>