-
Bug
-
Resolution: Fixed
-
Major
-
1.3.0
-
None
-
None
Steps to reproduce:
- Create new page
- Add Component-with-area (Note: add dialog to the definition to enable creating variant for this component)
- Not adding adding any nested components for Component-with-area and click create variant for it
- Result:
-
- On angular-sample: Cannot add components to the Component-with-area's variant, but it works fine on the original.
- On react-sample: The page cannot be displayed
Note: The vue-sample is working fine without issues.
Developer notes:
The issue could be area content is not created for variants in angular-editor and react-editor.
Workaround:
Create at least one nested component in the Component-with-area then create variants. In the variants, we can add more components and remove unused components but keep at least one component.
Acceptance criteria
- depends upon
-
MGNLPN-692 Create a variant-aware TemplateAnnotationEndpoint
- Closed
- relates to
-
PAGES-761 Personalization of components which contain areas with SPA Editor does not work
- Closed
-
MGNLFE-372 Creating component variant breaks editor JS
- Closed
1.
|
Implementation | Completed | Robert Šiška | |
2.
|
Review | Completed | Canh Nguyen | |
3.
|
Pre-Integration QA | Completed | Canh Nguyen | |
4.
|
QA | Completed | Javier Benito |