-
Improvement
-
Resolution: Done
-
Neutral
-
None
-
None
-
None
-
Empty show more show less
-
Yes
-
DevX 51
-
3
-
Yes
There is one use case need access mgnl:contentNode created by multifield but the inheritance nodes return the node has been renamed. See below image.
Screenshot 2023-11-10 at 09.24.56.png
Check inheritOnWithComplexDialog demo for freemarker/spa at https://git.magnolia-cms.com/projects/DOCUMENTATION/repos/component-inheritance-examples/pull-requests/3/diff#magnolia/content-to-import/website.FM-complex.yaml
Expectation request: Should not rename mgnl:contentNode in their case for easier to access the name of field in spa code.
Discussion:
There will be one case that if we config inheritance like below. PAGES rest can not support like freemarker is doing now.
inheritance:
enabled: true
components: all
nodeTypes:
- mgnl:component
- mgnl:contentNode
- caused by
-
PAGES-1314 Component inheritance not working for nested areas
- Closed