Inplace editing consolidation A: Bug-fixing (MGNLUI-259)

[MGNLUI-279] Tree crashes if property and child node have same name (same path) Created: 29/Nov/12  Updated: 02/May/13  Resolved: 17/Dec/12

Status: Closed
Project: Magnolia UI
Component/s: design
Affects Version/s: None
Fix Version/s: 5.0

Type: Sub-task Priority: Major
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-278 Cannot add new untitled property if t... Closed
is related to MGNLUI-1291 Cannot create a child node and a prop... Closed
Template:
Sprint: Iteration 2013-17, Beta 2

 Description   

When trying to create multiple child-nodes and properties in a row under a given node, the tree will inevitably crash miserably afterwards. This is due to having then a child node and a property with the same name ("untitled"), hence the same path (which is used as itemId in table).

Adding nodes and properties need to mutually check whether name is available on creating and renaming.



 Comments   
Comment by Mikaël Geljić [ 13/Dec/12 ]

Item creation is working fine after MGNLUI-278, now let's check item renaming.

Comment by Mikaël Geljić [ 13/Dec/12 ]
  • with nodes A and B, renaming A to B is not prevented, resulting in two nodes with name B, which JCR seems to be fine with (a JCR Query would show B, B[2], B[3]... though all these nodes do have name B. Somehow it's an array of Bs).
  • with properties A and B, renaming A to B is not prevented, resulting in deletion of property A and overwrite of property B with A's value.
  • with node A and property B, renaming A to B is not prevented, resulting in corrupted tree: node B is shown twice (i.e. on both rows), enabling you to expand both of them. This is the use case when the tree CRASHES, with messed-up table row indices and a nice exception in the stack trace.
Comment by Mikaël Geljić [ 31/Jan/13 ]

resolved long ago but with missing fixVersion, updated to s012. It's also the occasion to confirm resolution after vaadin7

Generated at Mon Feb 12 08:35:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.