[magnolia-dev] [JIRA] (MGNLUI-4213) NodesAndPropsDropConstraint doesn't take into account folder node
"JIRA (on behalf of Oanh Thai Hoang)" <jira-O8DnXSz/[email protected]>
| Newsgroups | gmane.comp.cms.magnolia.devel |
|---|---|
| Message-ID | <[email protected]> |
Oanh Thai Hoang created an issue Magnolia UI / https://jira.magnolia-cms.com/browse/MGNLUI-4213 MGNLUI-4213 NodesAndPropsDropConstraint doesn't take into account folder node Issue Type: Improvement Affects Versions: 5.5.3 Assignee: Unassigned Attachments: can-move-folder-inside-content-node.png, can-not-add-folder-inside-content-constraint.png Created: 25/May/17 5:52 AM Priority: Neutral Reporter: Oanh Thai Hoang Below case you can reproduce in Site app as well as Configuration app. - Prepare 2 folder node and 2 content node as following image https://jira.magnolia-cms.com/secure/attachment/39371/39371_can-not-add-folder-inside-content-constraint.png - Observe: Can't add folder inside content - Drag untitled0 folder inside untitled1 content node - Observe: folder can drag inside content node https://jira.magnolia-cms.com/secure/attachment/39370/39370_can-move-folder-inside-content-node.png - Expectation: folder can't drag inside content node. Drag drop behaviour must consistent with availability configuration (/modules/ui-admincentral/apps/configuration/subApps/browser/actions/addFolder/availability that prevent adding folder inside content) Source of problem: folder node in Config app is not really a real folder type. It is mgnl:content type https://jira.magnolia-cms.com/browse/MGNLUI-4213#add-comment Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) ---------- ---------------------------------------------------------------- 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: <[email protected]> ----------------------------------------------------------------
(unnamed)
(image/png, 952 B) - not displayed
(unnamed)
(image/gif, 98 B) - not displayed
(unnamed)
(image/png, 1.1 KB) - not displayed
(unnamed)
(image/png, 457 B) - not displayed
(unnamed)
(image/png, 2.9 KB) - not displayed