-
Improvement
-
Resolution: Incomplete
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Saigon 92, Saigon 93, Saigon 94, Saigon 95
-
5
As DEV-477 confirmed: there is redundancy between `DropConstraints` (dnd) and `MovePredicates` (move-dialogs), especially for their JCR implementations.
In a first step, we're able to delegate from MovePossibilityPredicates to a new default JCR DropConstraint;
then we try replacing move-predicates altogether with direct usage of the configured drop-constraint.
Lastly, old drop-constraint JCR impls may now extend the new one.
- caused by
-
MGNLUI-4170 Move Before and Move After buttons are disabled when moving node to its direct parent
- Closed
- is causing
-
CNTCTSAPP-102 Update the ContactDropConstraint to make it extends from JcrDropConstraint
- Closed
-
MGNLCAMPU-60 Update the CampaignDropConstraint to make it extends from JcrDropConstraint
- Closed
-
MGNLCAT-173 Update the CategorizationDropConstraint to make it extends from JcrDropConstraint
- Closed
-
MGNLDAM-714 Update the AssetsDropConstraint to make it extends from JcrDropConstraint
- Closed
-
MGNLGROOVY-162 Update the GroovyDropConstraint to make it extends from JcrDropConstraint
- Closed
-
MGNLGS-133 Update the GoogleSiteMapDropConstraint to make it extends from JcrDropConstraint
- Closed
-
MGNLINTEMPL-86 Update the InplaceTemplatingDropConstraint to make it extends from JcrDropConstraint
- Closed
-
MGNLPN-385 Update the SegmentDropConstraint to make it extends from JcrDropConstraint
- Closed
-
MGNLRSSAGG-212 Update the RSSAggregatorDropConstraint to make it extends from JcrDropConstraint
- Closed
-
PAGES-133 Update the TemplateTypeRestrictionDropConstraint to make it can reuse in the move dialog
- Closed
- is related to
-
MGNLSITE-79 "Move Before" and "Move After" buttons' states are not handled correctly
- Closed
- is superseded by
-
MGNLUI-4207 Replace move-predicates back with drop-constraints, and fix root availability
- Closed
- relates to
-
MGNLUI-4097 Selection should remain on the source node
- Closed