Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-11274] Replacing current outfit with contents of a non-outfit folder creates folder link in COF #1493

Open
sl-service-account opened this issue Jan 23, 2016 · 1 comment

Comments

@sl-service-account
Copy link

I am not sure if this is an intended behavior or a bug that sneaked in by oversight, so I'm filing this JIRA to get a clearification on the issue - or a fix is this is actually a bug. Try the following steps:

  1. Wear any outfit listed in the "Appearance" window
  2. Browse your inventory for any folder that is not a child of "My Outfits" and that contains any form of wearable items (objects or wearables)
  3. Right-click the folder and choose "Replace Current Outfit" from the context menu
  4. Open the "Current Outfit" folder in inventory and notice it contains a link to the folder you chose to replace the outfit with

http://i.imgur.com/o3RsrzO.png

Is this the correct and intended behavior? While it makes sense to have a link to the outfit folder for an actual outfit, it does not seem to be logical to do this for non-outfit folders. These non-outfit folders are in no way related to the list of outfits in the "Appearance" window. So if this the intended behavior, what is the purpose of creating this link even for no actual outfits?

This even creates another kind of issue where two folder links are being created in COF:

  1. Browse your inventory for any folder that is not a child of "My Outfits" and that contains any form of wearable items (objects or wearables)
  2. Right-click the folder and choose "Replace Current Outfit" from the context menu
  3. Open the "Current Outfit" folder in inventory and notice it contains a link to the folder you chose to replace the outfit with
  4. Open the "Appearance" window and click on "Save As" to create a new outfit
  5. Notice that now two folder links are in the "Current Outfit" folder: One linking to the original non-outfit folder, and a second, newly created folder link to the new outfit

http://i.imgur.com/zaqBduQ.png

Original Jira Fields
Field Value
Issue BUG-11274
Summary Replacing current outfit with contents of a non-outfit folder creates folder link in COF
Type Bug
Priority Unset
Status Accepted
Resolution Accepted
Reporter Ansariel Hiller (ansariel.hiller)
Created at 2016-01-23T14:01:26Z
Updated at 2016-01-25T17:48:57Z
{
  'Business Unit': ['Platform'],
  'Date of First Response': '2016-01-23T15:09:58.439-0600',
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'I am not sure if this is an intended behavior or a bug that sneaked in by oversight, so I\'m filing this JIRA to get a clearification on the issue - or a fix is this is actually a bug. Try the following steps:\r\n\r\n1. Wear any outfit listed in the "Appearance" window\r\n2. Browse your inventory for any folder that is not a child of "My Outfits" and that contains any form of wearable items (objects or wearables)\r\n3. Right-click the folder and choose "Replace Current Outfit" from the context menu\r\n4. Open the "Current Outfit" folder in inventory and notice it contains a link to the folder you chose to replace the outfit with\r\n\r\n!http://i.imgur.com/o3RsrzO.png!\r\n\r\nIs this the correct and intended behavior? While it makes sense to have a link to the outfit folder for an actual outfit, it does not seem to be logical to do this for non-outfit folders. These non-outfit folders are in no way related to the list of outfits in the "Appearance" window. So if this the intended behavior, what is the purpose of creating this link even for no actual outfits?',
  'What were you doing when it happened?': '-',
  'What were you expecting to happen instead?': '-',
}
@sl-service-account
Copy link
Author

Jim Tarber commented at 2016-01-23T21:09:58Z

The second part, the issue where the viewer creates more than one folder link in the Current Outfit folder, seems to be a serious problem since it causes further problems for viewers when they relog.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant