[
http://jira.magnolia.info/browse/MGNLDMS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18316#action_18316
]
Jan Haderka commented on MGNLDMS-137:
-------------------------------------
Hi Sunish,
as I explain earlier, Magnolia versions content only on the instance where
editing happens (the Author instance). If you need document to be also
versioned on the Public instance (instance from which content is served after
activation), it is technically possible to do, but you have to replace
ReceiveFilter (/server/filters/activation) on such public instance with your
own that would version the document before receiving new copy of it from the
Author instance.
Should you need some developer support to help you develop such filter, please
let us know what concrete assistance you need on support.
> 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/
----------------------------------------------------------------
