search

secondlife / jira-archive

2 stars 0 forks source link

[BUG-126] Renaming an item in an objects contents to a name of an already existing item in contents deletes the 1st item #2050

Open sl-service-account opened 12 years ago

sl-service-account commented 12 years ago

Steps to reproduce:

Observed Behaviour:

Item A gets deleted from prims contents If A was no copy - its gone for good

Expected Behaviour:

Both items remain in prims contents but a "1" is appended to item B's name

Reproduces on:

Links

Duplicates

Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-126 | | Summary | Renaming an item in an objects contents to a name of an already existing item in contents deletes the 1st item | | Type | Bug | | Priority | Unset | | Status | Accepted | | Resolution | Released | | Reporter | Whirly Fizzle (whirly.fizzle) | | Created at | 2012-09-18T07:01:34Z | | Updated at | 2014-03-10T21:29:51Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2012-09-18T02:18:38.793-0500', "Is there anything you'd like to add?": 'blah', 'Regression?': ['Issue is a Regression'], 'System': 'SL Simulator', 'Target Viewer Version': 'viewer-development', 'What just happened?': 'will fill out once filed', 'What were you doing when it happened?': 'blah', 'What were you expecting to happen instead?': 'blah', 'Where': 'Happens on all server channels', } ```
sl-service-account commented 12 years ago

TankMaster Finesmith commented at 2012-09-18T07:18:39Z

Just to reiterate, this is content loss. If you rename the item again, the original item does not reappear, same with taking and re-rezzing the object. Once the object disappears, there is no apparent way to get it back.

sl-service-account commented 12 years ago

Miro Collas commented at 2012-09-18T07:21:37Z

To further add: deleting the single remaining object also doesn't make the other one reappear.

Reported behavior confirmed, main channel region.

sl-service-account commented 12 years ago

MartinRJ Fayray commented at 2012-09-18T08:31:21Z

Also reproduced on Second Life 3.4.0 (264700) Sep 12 2012 17:21:16 (Second Life Release), Second Life Server 12.09.04.264357

Also reproduced on other server channels: Second Life RC BlueSteel 12.09.07.264510 Second Life RC Magnum 12.09.07.264510 Second Life RC LeTigre 12.09.07.264510

sl-service-account commented 12 years ago

Maestro Linden commented at 2012-09-18T21:50:04Z

Hi Whirly, thanks for the report. Trying this on the past few main channel releases, I can reproduce this on 12.09.04.264357, but not on 12.08.14.263480; it would appear that 12.09.04.264357 introduced this bug, since there were no releases between them.

sl-service-account commented 12 years ago

Moon Metty commented at 2012-09-19T03:51:50Z

Here's an interesting observation http://www.sluniverse.com/php/vb/sl-jira-issue-discussion/76347-bug-126-renaming-item-object.html#post1637501

Iain Maltz: "Heh, fascinating, did you notice the 2nd item isn't actually properly deleted?

Make prim, click "new script" twice, rename "New Script 1" to "New Script", click item. Both say "Touched"...

If you then de-rez the object and re-rez it you have two scripts called "new script" and "old script" oO"

Good thing we have the shadow-jira ...

sl-service-account commented 12 years ago

Whirly Fizzle commented at 2012-09-19T04:37:35Z

I think thats probably what Martin saw a few days ago when he commented on SCR-118 about the return of the mysterious "Old Script"

https://jira.secondlife.com/browse/SCR-118?focusedCommentId=344625&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-344625