Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-387

TemplateSelectorField queries for available templates using the wrong node

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 5.0
    • None
    • forms
    • None

    Description

      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.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                fgrilli Federico Grilli
                tmattsson Tobias Mattsson
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD