[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka updated MAGNOLIA-3704:
----------------------------------
Fix Version/s: Backlog
(was: 4.4.x)
> versioning: clean mgnlVersions workspace after versioning
> ---------------------------------------------------------
>
> Key: MAGNOLIA-3704
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3704
> Project: Magnolia
> Issue Type: Improvement
> Security Level: Public
> Components: activation, core
> Reporter: Philipp Bärfuss
> Priority: Major
> Fix For: Backlog
>
>
> When we version we clone the node and its children to mgnlVersions based on
> rules. We clone paragraphs together with the page but not the subpages. If
> this rules are not applied consequently then it can happen that a node we are
> activating/versioning already exists as a subnode of another node and then
> the process fails.
> We had several issues related to the DMS with this but currently again in the
> Data module (MGNLDATA-124).
> Since this nodes are just handles to the version history after we versioned
> the content, we could simply purge all content of the node after the
> versioning.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
