topic Re: CIFS not adding 'versionnable' aspect in Alfresco Archive

CIFS not adding 'versionnable' aspect

jservajean — Wed, 13 Aug 2014 13:26:04 GMT

I'm facing two different behaviours whether I had offices files from the CIFS or from the Share client :1 - If I initially create a Word document using Share, then all the consecutive updates (no matter how, from CIFS or Share) will result in the version (1.0, 1.1, etc.) beeing automatically increme

Re: CIFS not adding 'versionnable' aspect

mrogers — Wed, 13 Aug 2014 13:49:17 GMT

No. It's a feature of share that it lazy versions.

If you need to make everything versionable then define it via a rule (like share should have done)

Re: CIFS not adding 'versionnable' aspect

jservajean — Wed, 13 Aug 2014 14:35:27 GMT

Thx for the reply

Just any idea on where and where it is defined in Share ? I'd like to reproduce the default behaviour even when using CIFS (it seems Alfresco adds versionnable aspects on selected mimetypes, eg. MS Office).

There's no default content rule of that kind, to my knowledge. I'd have rather bet on a policy/behaviour kind of intregation, but in that case it should be triggered server-side, so CIFS should trigger it, right ?

Re: CIFS not adding 'versionnable' aspect

mrogers — Wed, 13 Aug 2014 15:44:00 GMT

Its hard coded into share. As is the starting of versions as 1.0.

Re: CIFS not adding 'versionnable' aspect

jservajean — Tue, 16 Sep 2014 08:51:23 GMT

Any idea of the name of the svn project to look into and/or the webscript/class/javascript if it's not too much to ask ?
thx