topic Re: Content without Versioning in Alfresco Archive

Content without Versioning

orbitron — Mon, 24 Jan 2011 08:34:58 GMT

Hello,I am using 4.3.c Community edition.My main purpose is change the initial version of a Document. When you upload a new "Content" it always start with version "1.0". It will be a nice feature for future versions if you could choose the inital version (i.e "0.1").Finding a workaround:I have insta

Re: Content without Versioning

_sax — Thu, 27 Jan 2011 13:22:41 GMT

I didn't exactly notice this before. When uploading a document with the classic client (server:8080/alfresco), no versioning is applied. When viewing that file within the Share client (server:8080/share), it says, that it's version 1.0, but it still has no cm:versionable aspect applied. If updating the file in the Share client, it automatically asks, if you want to create a minor (1.1) or major revision (2.0) and applies that, if you update it. It then has the cm:versionable aspect, as verifiable with the classic client.

So at first, Share only says there is a versioning (1.0), when there isn't. It only adds it, even if not told to.
I presume, there's only source code editing left for you, if there is no option to turn Share auto versioning off, in http://wiki.alfresco.com .

Re: Content without Versioning

pmonks — Fri, 28 Jan 2011 06:51:49 GMT

Keep in mind that the version baselining extension was developed for an earlier version of Alfresco (3.2, from memory), and specifically for the Explorer UI. As mentioned above, the Share UI automatically adds the cm:versionable aspect to the content nodes it creates, making it more difficult (but not necessarily impossible) to force a particular version number to be the baseline.

I've not received any requests to update the version baselining extension for newer versions of Alfresco, let alone enhance it to work with the Share UI, but I'd welcome anyone who wishes to contribute to the Google Code Project [1] to extend it in either of these ways.

Cheers,
Peter

[1] http://code.google.com/p/alfresco-version-baselining/

Re: Content without Versioning

ruighr — Mon, 06 Feb 2012 17:09:27 GMT

Just a small clarification–the Share UI doesn't set cm:versionable on the first upload of a file. So if you check the version2store with the node browser, there won't be anything there. When a file is later updated, Share sets cm:versionable just before the update, after which the version2store will have both the original and updated versions. I suspect the developers were trying to save space in the version2store, but IMHO it just complicates everything…

Re: Content without Versioning

mrogers — Mon, 06 Feb 2012 18:19:00 GMT

No it was done in the name of performance. And yes it does complicate things. :roll:

You can plug your own version policies into the version service however last time I looked Share completely ignored them.

This is a bit of a "hot potato" issue - better shut up now.