Details
-
Bug
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
UI FW 5, UI FW 6
-
3
Description
From what it looks like the converted chooser gets its datasource definition resolved only via the specified app's content connector definition, but the old link field actually also allows specifying `workspace` and `rootPath` properties explicitly and those aren't considered by the converter.
AC:
- mentioned two properties are handled (:?: and passed to the CompatibilityAppAwareWorkbenchChooserDefinition#resolveDatasourceFromAppName)
- test case is written (can piggyback on the linked Blossom issue)
Checklists
Acceptance criteria
Attachments
Issue Links
- is related to
-
MGNLUI-6199 "targetTreeRootPath" Property Is Affecting Pages App Hierarchy When Included On A Magnolia 5UI Dialog Containing A Link Field
-
- Closed
-