-
Task
-
Resolution: Done
-
Neutral
-
None
-
6.2
-
None
-
-
Empty show more show less
-
Empty show more show less
-
UI FW 13
-
2
We want to avoid currentItemProvider usage with multis (may look for other candidates from code perspective in ConfiguredComplexPropertyDefinition), b/c it leads to issues like MGNLUI-5886.
The multi nodes could then be resolved by multiple fields that are using currentItemProvider, if they would resolve the same nodes - effectively overwriting each other's contents. Another problem that would result from using currentItemProvider is that if the multi field would be set to resolve non-strictly (strict property set to false, which is the default), the multi would be resolving irrelevant nodes (everything in the parent) which would result in errors.
One such place where this could be noted is in
https://documentation.magnolia-cms.com/display/DOCS62/Field+definition#Fielddefinition-Commonfieldproperties. Also present here https://documentation.magnolia-cms.com/display/DOCS62/Item+providers though some clarification is already next to it, to it might be better to make it clearer.
- relates to
-
MGNLUI-6316 DOC: Default to jcrChildNodeProvider in jcrMultiField
- Closed
-
MGNLUI-6320 DOC: Using currentItemProvider in complex fields
- Closed
-
MGNLUI-6332 DOC: Better explanation of itemProvider on multi field page
- Closed
-
MGNLUI-6285 Consider notifying in Definition's app when using CurrentItemProvider in inappropriate contexts
- Open