[ 
http://jira.magnolia-cms.com/browse/MGNLUI-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tobias Mattsson updated MGNLUI-387:
-----------------------------------

    Component/s: forms

> TemplateSelectorField queries for available templates using the wrong node
> --------------------------------------------------------------------------
>
>                 Key: MGNLUI-387
>                 URL: http://jira.magnolia-cms.com/browse/MGNLUI-387
>             Project: Magnolia UI
>          Issue Type: Bug
>      Security Level: Public
>          Components: forms
>            Reporter: Tobias Mattsson
>            Assignee: Federico Grilli
>            Priority: Critical
>             Fix For: 5.0 Alpha2 s011
>
>
> In 4.5 the node was created and assigned the default template, only 
> afterwards did the user make a selection by changing the template in the 
> template column.
> In 5.0 we're instead presenting a dialog first where the user can select the 
> template to assign to the node once its created.
> This has produced a bug in the current code base where TemplateSelectorField 
> queries for available templates using the parent node.
> info.magnolia.rendering.template.assignment.TemplateDefinitionAssignment#getAvailableTemplates(Node)
>  is not supposed to be used to test for available nodes in _children_ of the 
> passed 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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to