[
http://jira.magnolia.info/browse/MGNLDMS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18310#action_18310
]
Olivier Marti commented on MGNLDMS-137:
---------------------------------------
Hey Sunish
Well, there is no difference from an author to a public instance, expect the
fact that it is configured as a public instance.
The "problem" with versioning is just that on an activation of a document
(data, website) only the current version is the one which get's activated.
Think of like you activate a document which has ten versions...not the best
approach for a performant activation process though.
For your scenario it may be a better approach to upload the different document
versions seperately (as 1.0, 1.1, ...).
> Magnolia public instance does not contain versioned documents
> -------------------------------------------------------------
>
> Key: MGNLDMS-137
> URL: http://jira.magnolia.info/browse/MGNLDMS-137
> Project: Magnolia DMS Module
> Issue Type: Improvement
> Reporter: Sunish Abraham
> Assignee: Philipp Bracher
> Priority: Critical
>
> versions documents in source DMS activated does not carry the versioned
> information to the destination instance ; we have functionality in the Author
> environment of the destintation instance which requires the documents to be
> versioned
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
