[MGNLDATA-123] GenericDataAdminTree should include dataItemNode type on default Created: 10/May/11  Updated: 19/Oct/11  Resolved: 18/May/11

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 1.6.2
Fix Version/s: 1.6.3

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

Issue Links:
relation
is related to MGNLDATA-134 Allow bunch activation of items which... Closed
supersession
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When activating data with dataItemNode as children (e.g. some category) that children is skipped during activation.
Workaround for this behaviour is to register dataItemNode type under tree configuration of data type (property itemTypes).



 Comments   
Comment by Jan Haderka [ 16/May/11 ]

info.magnolia.module.data.DataConsts already contains constant for the dataItemNode, no need to introduce it again.
Also the check itself will now incorrectly return true if set type name is superstring to dataItemNode like mydataItemNode}} or similar. Values in the list should be tokenized by {{, }} (comma and space) and token should be then checked for exact match.

Comment by Jan Haderka [ 18/May/11 ]

all good except, please use java.util.Arrays instead of

import edu.emory.mathcs.backport.java.util.Arrays;
Generated at Mon Feb 12 05:11:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.