[PAGES-96] Magnolia saves the "position" attribute to newly added component Created: 20/Sep/16  Updated: 21/Nov/16  Resolved: 18/Nov/16

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: 5.4.9, 5.5.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
is cloned by MGNLPN-346 CLONE - Magnolia saves the "position"... 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
Date of First Response:
Sprint: Kromeriz 71
Story Points: 3

 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



 Comments   
Comment by Christian Ringele [ 05/Oct/16 ]

I think a property should have been chosen, that is 100% not used by customer project's, something alike: mgnl_init_position or alike.

And the property should be cleaned/removed from all the components of the same area after:

  • a new component is added
  • a move operation on the components have been done
Generated at Mon Feb 12 06:15:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.