[MGNLPN-346] CLONE - Magnolia saves the "position" attribute to newly added component Created: 15/Nov/16  Updated: 21/Nov/16  Resolved: 18/Nov/16

Status: Closed
Project: Magnolia Personalization
Component/s: Component p13n
Affects Version/s: 1.3, 1.4
Fix Version/s: 1.3.1, 1.4.1

Type: Bug Priority: Neutral
Reporter: Tom Wespi Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2016-09-20 at 11.35.49.png    
Issue Links:
Cloners
clones PAGES-96 Magnolia saves the "position" attribu... Closed
causality
caused by PAGES-59 Allow to add components also at the t... Closed
dependency
is depended upon by PAGES-64 Ask a user where to add a new compone... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Sprint: Kromeriz 71
Story Points: 2

 Description   

When adding a new component, magnolia asks if the component should added at top or at bottom of the area.

If the dialog has a field (e.g. Text Field) with the name «position», it gets filled with either «top» or «bottom».

If the field is a select field with the values

  • left (selected)
  • right
    no value is selected when creating a new component, due the value of «position» is already set to «top» or «bottom». This behaviour leaded to many problems in our projects.

This value get also stored to the component, which makes absolutely no sense, due the component may be moved afterward.

Tested on demoauthor


Generated at Mon Feb 12 06:36:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.