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

Move action does not contain DropConstraint configuration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 6.2.18
    • 6.2.17
    • None

      Steps to reproduce

      1. Create a constraint on a content app to restrict which nodes can be moved inside e.g, at Assets app switch the mgnl:asset primaryNodeType to mgnl:folder
      2. Go to the app (Asset) and drag and item within other which should not be allowed (an asset within other asset)
      3. Check Drag and Drop allows it
      4. Now click on another item (asset) and clic on Move action on the action bar (or right click -> Move)
      5. Check that moving an asset inside another one is not allowed

      Expected results

      Drag and Drop movement and Move action behaves the same

      Actual results

      Drag and Drop movement and Move action do not apply the same rules when moving items

      Workaround

      N/A

      Development notes

      This is just an example with the Assets app. In the linked ticket, there is a full example and the definition needed to reproduce it in a custom content app

        Acceptance criteria

              sang.ngo Sang Ngo Huu
              ccantalapiedra Carlos Cantalapiedra
              Nucleus
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - Not Specified
                    Not Specified
                    Logged:
                    Time Spent - 1.75d
                    1.75d