Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-500

DialogMVCHandler cannot handle arbitrary nodeCollections as target

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • 2.1 Final
    • 2.1 Final
    • admininterface
    • None
    • all

      The DialogMVCHandler has lost a feature compared to previous releases. It is less general.

      It is not possible anymore to target any content container to store data entered through a dialog.

      Following patch reintroduces this feature:

      — originals/magnolia-2.1-SNAPSHOT/src/main/info/magnolia/module/admininterface/DialogMVCHandler.java 2005-07-13 17:15:08.000000000 +0200
      +++ patched/magnolia-2.1-SNAPSHOT/src/main/info/magnolia/module/admininterface/DialogMVCHandler.java 2005-07-24 19:19:18.000000000 +0200
      @@ -217,9 +217,14 @@
      try {
      Content parentContent = hm.getContent(path);
      if (StringUtils.isEmpty(nodeName)) {
      + if (StringUtils.isEmpty(nodeCollectionName))

      { storageNode = parentContent; }

      else

      { + storageNode = parentContent.getContent(nodeCollectionName); + }

      + }
      + else {
      if (StringUtils.isEmpty(nodeCollectionName)) {
      storageNode = parentContent.getContent(nodeName);

        Acceptance criteria

              pbaerfuss Philipp Bärfuss
              aemi Michael Aemisegger
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD