[
http://jira.magnolia-cms.com/browse/MGNLDATA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka reopened MGNLDATA-123:
----------------------------------
{{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.
> GenericDataAdminTree should include dataItemNode type on default
> ----------------------------------------------------------------
>
> Key: MGNLDATA-123
> URL: http://jira.magnolia-cms.com/browse/MGNLDATA-123
> Project: Magnolia Data Module
> Issue Type: Bug
> Affects Versions: 1.6.2
> Reporter: Ondřej Chytil
> Assignee: Ondřej Chytil
> Priority: Major
> Fix For: 1.6.3
>
>
> 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}}).
--
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]>
----------------------------------------------------------------
