-
Bug
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
DevX 50
-
3
-
Yes
The area properties "type:single" and "maxComponents" work inconsistantly when using "Component Inheritance" in Freemarker and in headless mode.
(Before changing behaviour: consider how changing the behaviour could impact existing customers.)
Expectation:
Inherited components are treated just like actual components in an area as regards to those two properties.
- If "type:single", and an area has an inherited component, then an author cannot add any more components.
- If "maxComponents:1" and an area has an inherited component, then an author cannot add any more components.
- if "maxComponents:3" and an area has an inherited component, then an author can only add 2 more components to the area.
Current behaviour:
In all cases, the area already has 1 inherited component.
Freemarker with maxComponents:1 -> Author can add another component. (Unexpected.)
Freemarker with type:single -> Author cannot add another component. (As expected.)
SPA with maxComponents:1 -> Author can add another component. (Unexpected.)
SPA with type:single -> Author can add another component. (Unexpected.)
Notes:
This demo project may be useful for this bug: https://git.magnolia-cms.com/projects/DOCUMENTATION/repos/component-inheritance-examples/browse
- is cloned by
-
PAGES-1494 Area Inheritance: maxComponents and type:single inconsistant
- Closed
- relates to
-
MAGNOLIA-9156 Area Inheritance - SPA: Users can add another component when a single type area which has inherited components
- Closed
- mentioned in
-
Page Loading...
1.
|
Implementation | Closed | Oanh Thai Hoang |
|
||||||||
2.
|
Review | Completed | Anh Vu | |||||||||
3.
|
Pre-Integration QA | Closed | Anh Vu | |||||||||
4.
|
QA | Completed | Canh Nguyen |