[
http://jira.magnolia.info/browse/MGNLDMS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18245#action_18245
]
Sunish Abraham commented on MGNLDMS-137:
----------------------------------------
When we use admin central of public instance, we are able to upload multiple
versions of the document. So it is not the public instance that prohibits
versioning, it is the subscriber that is not versioning the incoming content.
Just thinking on these lines....
- The JCRs are meant for storing versioned documents. (This comment is
irrespective of magnolia author or public)
- The versioning can be enabled or disabled in magnolia public using admin
central.
So if public instances are not meant for versioning, then why do we have the
feature of enabling/ disabling versioning in public instance?
> 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/
----------------------------------------------------------------
