[
http://jira.magnolia-cms.com/browse/MGNLDATA-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24336#action_24336
]
Bert Leunis commented on MGNLDATA-71:
-------------------------------------
I ran into another problem concerning this trees / types / dialogs
configuration. If you have type A with subtype B, you will see the created
types A and B in the tree of type A. When opening a dialog for type B, the
dialoghandler for type A is used. This is because the name of the tree is used
to retrieve the dialog definition
(info.magnolia.module.admininterface.DialogMVCServlet.getHandler()). So in
this case the configured saveHandler for the dialog type A is used, not the
one you configured for type B. used. In this case the itemType of the type to
be edited should be used?
I'm not really sure about this because the creation of trees, dialogs etc is
quite complicated.
> Don't create extra trees for subtypes
> -------------------------------------
>
> Key: MGNLDATA-71
> URL: http://jira.magnolia-cms.com/browse/MGNLDATA-71
> Project: Magnolia Data Module
> Issue Type: Sub-task
> Reporter: Jan Haderka
> Assignee: Philipp Bärfuss
>
> as those can't exist in a tree like hierarchy on their own anyway.
--
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]>
----------------------------------------------------------------
