I have a situation where I would like to be able to create a new version of my content node without publishing the node.
The reason behind it is that I would like to let the user use the Rollback feature to see what has changed between saves, and not only between published versions (It has the nice diff view).
This would be very useful in the following translation scenario:
1: Content is created in global site 2: Content is copied to local sites, and related to original 3: Local version is translated and published 4: Original version is updated, and properties are saved to the related local versions (overwriting the translation) 5: Local editor needs to identify changes to original document
At step 5, the local editor will now only see the first translated version, and the new content from the original version. So there is no diff view between the first original, and the latest original.
If I could stamp a version number on the first translations that I copy to the local sites, then they would appear in the version history, and could be compared to new content.
It seems, that if I do a quick publish/unpublish in the businesslogic, then it does not check if the parent has been published. So I just do it right after each other, and I get my version stamp:
d.Publish(new User(0));
d.UnPublish();
No publishing to runtime or anything. Just a DB version stamp.
Stamping new version ID without doing a publish
I have a situation where I would like to be able to create a new version of my content node without publishing the node.
The reason behind it is that I would like to let the user use the Rollback feature to see what has changed between saves, and not only between published versions (It has the nice diff view).
This would be very useful in the following translation scenario:
1: Content is created in global site
2: Content is copied to local sites, and related to original
3: Local version is translated and published
4: Original version is updated, and properties are saved to the related local versions (overwriting the translation)
5: Local editor needs to identify changes to original document
At step 5, the local editor will now only see the first translated version, and the new content from the original version. So there is no diff view between the first original, and the latest original.
If I could stamp a version number on the first translations that I copy to the local sites, then they would appear in the version history, and could be compared to new content.
Answering my own question here...
It seems, that if I do a quick publish/unpublish in the businesslogic, then it does not check if the parent has been published. So I just do it right after each other, and I get my version stamp:
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.