As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
node.addMixin("cm:versionable"); node.setProperty("cm:autoVersion", true);
You need to make sure your first version is a major version rather than a minor version.(There's an extra property to set)
No the previous behaviour was incorrect and has been fixed. The first minor version should be 0.1 rather than 1.0. The first major version will still be 1.0, that is unchanged.
Found another related 'issue' (i'm using alfresco 4.0.0 (3979))If the versionable aspect is applied using a rule, and the document is added using explorer, 3 possible outcomes, depending on the wizardCase 1: You upload the file, and then you unmark the 'Modify all properties when this page closes.' the document is loaded with version 0.1Case 2: You upload the file, and then you leave the 'Modify all properties when this page closes.' and you unmark the 'Auto Version' the document is loaded with version 0.1Case 3: You upload the file, and then you leave the 'Modify all properties when this page closes.' and leave the 'Auto Version' the document is loaded with version 0.2Case 3 is really odd. I also found that the properties memorized in the 0.1 are the ones written in the first page (for example, name property is present in both pages). Makes sense, but imho there should be only one version.
So in any case the first version of the document is 1.0?