Version history is not saving any more.

[anele]

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. The only thing that helps is to reupload the document again, but I don't like this decision since all the history will be lost.
Is there a way to fix it without loosing the history?

[afaust]

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?

[anele]

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).

[afaust]

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.

[anele]

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?

[afaust]

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.

[anele]

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

[afaust]

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).

[anele]

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.  

[afaust]

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