[
http://jira.magnolia-cms.com/browse/MGNLDMS-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21946#action_21946
]
Jan Haderka commented on MGNLDMS-158:
-------------------------------------
The issue is that the type of {{description_files}} node is a
{{mgnl:contentNode}} and the default {{Rule}} allows only for
{{mgnl:contentNode}}, {{mgnl:resource}} and {{mgnl:metaData}}
({{RuleBasedCommand.getRule()}}).
When versioning recursively, we reverse the rule to exclude children that have
to be versioned on their own from those that need to be versioned with the
current node (anonymouse {{ContentFilter}} in
{{VersionCommand.versionRecursively()}}). This in turn excludes
{{description_files}} node from the list of children that need to be versioned
with its parent content node. Since the {{description_files}} node is not in
the original list of nodes to be versioned either there is node missing by the
end of versioning.
There might be actually two separate issues at play here as sometimes the
message is {{.../description_files node is missing}} and sometimes the
{{.../description_files/MetaData node is missing}}
While the above explanation of the issue might not be fully correct yet, issue
is reproducible with clean installation of DMS 1.3 as well as with upgrade from
previous versions and is likely related to the rules and node selection during
versioning rather then to node type definition.
> Versioning of document with content in Description field fails
> --------------------------------------------------------------
>
> Key: MGNLDMS-158
> URL: http://jira.magnolia-cms.com/browse/MGNLDMS-158
> Project: Magnolia DMS Module
> Issue Type: Bug
> Affects Versions: 1.2.7, 1.3
> Reporter: Jan Haderka
> Assignee: Jan Haderka
> Fix For: 1.3.1
>
>
> When document is added to DMS such that it contains content in the
> "Description" field of type FCKEdit, the associated {{description_files}}
> node is created. When parent of such document is activated including
> subnodes, recursive versioning operation is performed and fails when trying
> to version the {{description_files}} node, versioning fails with message
> {{Mandatory MetaData is missing}}. Export of the document shows that meta
> data is present on this node.
--
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/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
