[MGNLDMS-158] Versioning of document with content in Description field fails Created: 24/Mar/09  Updated: 03/Jul/14  Resolved: 27/Mar/09

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: 1.2.7, 1.3
Fix Version/s: 1.4

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
dependency
depends upon MAGNOLIA-2672 Expose filter used in VersionCommand ... Closed
duplicate
is duplicated by MAGNOLIA-2408 DMS-Activation - can't version: /desc... Closed
relation
is related to MGNLDMS-140 Error message when publishing a folde... Closed
is related to MAGNOLIA-2910 Preserve DMS specific versioning comm... Closed
is related to MAGNOLIA-2955 CLONE -Preserve DMS specific versioni... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

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.



 Comments   
Comment by Jan Haderka [ 24/Mar/09 ]

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.

Comment by Jan Haderka [ 27/Mar/09 ]

Done as of r24020.

Comment by CSC CWMP Support [X] (Inactive) [ 16/Oct/12 ]

Attachments as per request.
Unfortunately DMS seems to be 1.4

Generated at Mon Feb 12 00:48:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.