Webdav versioning problem

[art99trash]

I am having an issue with versioning files that are updated through Webdav.

Using Community 5 with Postgresql.

When a file has been created and is at the 1.0 version, if a user updates the file through webdav, the version does not change. It just overwrites the file. However, if a new version is uploaded through the Alfresco Share client interface, subsequent webdav updates create new versions.

It's as though the Share update turns on versioning.

Has anyone seen this problem?

Thanks.

[afaust]

Your assumption is correct. When you upload a document via WebDAV it will not be versioned by default. The "1.0" label you are seeing in the UI is basically a "dummy" at this point because in a non-versioned document any current state is always the one and only version of that document.

When you upload a new version via Share, it will add the necessary aspect for the document to be considered versionable.

Versioning can be a quite confusing concept, especially when you are dealing with multiple interfaces. Last year at the BeeCon hackathon a few people worked on documenting the behaviour and potential improvements.

[art99trash]

Axel, thank you for the reply.

Are you saying that there is no way to get the file versioning to work without updating the file 

through the client interface?

I would like to create and update files, using only Webdav, and have file versioning working.

Thanks.

[afaust]

You can always create a behaviour (using Java based programming) to automatically apply / enable versioning on all files. The challenge here is to differentiate between actual files (managed via Share UI or WebDAV) and stuff that Alfresco handles transparently "just like" files.