topic Re: Version history is not saving any more. in Alfresco Archive

Version history is not saving any more.

anele — Tue, 29 Nov 2016 06:35:06 GMT

Hello! One of my alfresco sites suddenly stopped updating version history for documents created by a certain user. It happens when other users try to edit these documents online, no new version appears in history but the changes themself are saved, when editing offline version history gets saved. Th

Re: Version history is not saving any more.

afaust — Tue, 29 Nov 2016 15:56:31 GMT

Can you provide any more information on the affected documents? I.e. in what path below the site are they stored (I believe the documentation states that there may be issues with files stored at the top level) and what aspects / properties regarding the cm:versionable aspect are set?

Also, what Alfresco version and SharePoint module are you using? The newer AOS or legacy VTI?

Re: Version history is not saving any more.

cesarista — Tue, 29 Nov 2016 17:48:57 GMT

Maybe this is related and helps:

If you edit inline (in Alfresco) a new text file created via Alfresco Share UI for example, or you edit online (via webdav with Libreoffice addon) and versionable aspect is not applied, there is NOT a new version saved, and no version history (I did not test it neither in AOS nor VTI because I am in a Linux stack). Maybe this is happening to you. In these cases, it is useful to apply versionable aspect via content rule to certain editable mimetypes when added or created, or adding versionable aspect to a node template depending on your case for creating content.
If you edit offline or upload a new version from Alfresco Share, you obtain a new version and the corresponding history, cause these actions are applying versionable aspect implicitely.

Regards.

--C.

Re: Version history is not saving any more.

anele — Wed, 30 Nov 2016 07:19:31 GMT

Thanks for reply. The versionable aspect seems to be set. After reapplying this aspect for one document the versioning is working again, but the history is lost. Is there a way to force this aspect without loosing the history?
Considering the path, there are many documents in documentlibrary itself and in its subfolders.
The version of alfresco I'm using is 5.2.0 (r125711-b6).

Re: Version history is not saving any more.

anele — Wed, 30 Nov 2016 07:43:01 GMT

I've tried to apply versionable aspect via content rule as you suggested but it had no effect.( Probably because it's already been applied. Reapplying the aspect helps to make versioning work but all the previous history gets lost.

Re: Version history is not saving any more.

afaust — Wed, 30 Nov 2016 07:45:51 GMT

Then it appears that the versionable properties are set to a value that prevents creation of new versions. Instead of removing and reapplying the aspect, simply set the cm:autoVersion property to true if it is currently false.

Re: Version history is not saving any more.

anele — Wed, 30 Nov 2016 08:25:39 GMT

You mean version.store.enableAutoVersioning=true in alfresco-global.properties? Or is there another place to configure it? Is'n true supposer to be a default value?

Re: Version history is not saving any more.

afaust — Wed, 30 Nov 2016 09:29:31 GMT

No - I meant what I said: the cm:autoVersion node property. This is defaulted to the value of version.store.enableAutoVersioning but may be overriden on a per-node basis.

Re: Version history is not saving any more.

anele — Wed, 30 Nov 2016 09:53:58 GMT

So how do I set cm:autoVersion to true? Where?

Re: Version history is not saving any more.

afaust — Wed, 30 Nov 2016 10:17:55 GMT

Either via the JavaScript console or "Edit Properties" (default metadata forms do not show that property though so you would have to configure one yourself).

Re: Version history is not saving any more.

anele — Fri, 02 Dec 2016 07:26:36 GMT

Sorry for a late reply. Can you explain me how create a new property or give a link to some tutorial? I can't find any.

Re: Version history is not saving any more.

afaust — Fri, 02 Dec 2016 07:32:35 GMT

The property already exists. You would only have to configure a form for it to be editable.