You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 28, 2024. It is now read-only.
Scrolling through the region Top Scripts list, selecting and disabling scripted objects with a high region impact, However only some objects became disabled. There is no explanation to how it is not properly disabling any selected object, the conditions are unclear.
Actual Behavior
It appears that the functionality no longer properly works for the Disable Selected button.
The Disable Selected and Disable All button functionallity in Top Scripts menu in Region/Estate should stop the scripts running in the selected offending object/objects. It only seems to disable objects in certain conditions, Conditions in which are not very clear as it does work for some objects owned by others on other parcels.
Expected Behavior
The Disable Selected functionality button in Top Scripts should be able to disable any selected object chosen by the Estate Owner or Estate Manager as it usually did.
Other information
It allows region administrators to manage objects in the region more efficiently and effectively. Especially when dealing with objects that impact the server performance so much that it will not let you return them.
The Disable Selected feature was working before fully but for some reason no longer has been working properly for quite some time now.
I have tried various conditions for an explanation on the issue:-
Residents object is in the land group.
Residents object is in another parcel.
Residents object is on the same parcel but not in the group.
Resident is not in the group with objects on the parcel.
My own objects on the same parcel not set to group.
My own objects set to group in another parcel.
Original Jira Fields
Field
Value
Issue
BUG-37767
Summary
"Disable Selected" Button Functionallity in Top Scripts - Region/Estate Menu
Type
Bug
Priority
Unset
Status
Accepted
Resolution
Accepted
Reporter
Seanas Alston (seanas.alston)
Created at
2016-09-02T17:30:27Z
Updated at
2016-09-09T21:47:46Z
{
'Business Unit': ['Platform'],
'Date of First Response': '2016-09-09T16:47:37.892-0500',
"Is there anything you'd like to add?": 'It allows region administrators to manage objects in the region more efficiently and effectively. Especially when dealing with objects that impact the server performance so much that it will not let you return them. \r\n\r\nThe Disable Selected feature was working before fully but for some reason no longer has been working properly for quite some time now.\r\n\r\nI have tried various conditions for an explanation on the issue:- \r\nResidents object is in the land group. \r\nResidents object is in another parcel. \r\nResidents object is on the same parcel but not in the group.\r\nResident is not in the group with objects on the parcel.\r\nMy own objects on the same parcel not set to group.\r\nMy own objects set to group in another parcel.',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'System': 'SL Simulator',
'Target Viewer Version': 'viewer-development',
'What just happened?': 'It appears that the functionality no longer properly works for the Disable Selected button. \r\n\r\nThe Disable Selected and Disable All button functionallity in Top Scripts menu in Region/Estate should stop the scripts running in the selected offending object/objects. It only seems to disable objects in certain conditions, Conditions in which are not very clear as it does work for some objects owned by others on other parcels.',
'What were you doing when it happened?': 'Scrolling through the region Top Scripts list, selecting and disabling scripted objects with a high region impact, However only some objects became disabled. There is no explanation to how it is not properly disabling any selected object, the conditions are unclear.',
'What were you expecting to happen instead?': 'The Disable Selected functionality button in Top Scripts should be able to disable any selected object chosen by the Estate Owner or Estate Manager as it usually did.',
'Where': 'http://maps.secondlife.com/secondlife/Unknown%20Region/128/128/35',
}
The text was updated successfully, but these errors were encountered:
Steps to Reproduce
Scrolling through the region Top Scripts list, selecting and disabling scripted objects with a high region impact, However only some objects became disabled. There is no explanation to how it is not properly disabling any selected object, the conditions are unclear.
Actual Behavior
It appears that the functionality no longer properly works for the Disable Selected button.
The Disable Selected and Disable All button functionallity in Top Scripts menu in Region/Estate should stop the scripts running in the selected offending object/objects. It only seems to disable objects in certain conditions, Conditions in which are not very clear as it does work for some objects owned by others on other parcels.
Expected Behavior
The Disable Selected functionality button in Top Scripts should be able to disable any selected object chosen by the Estate Owner or Estate Manager as it usually did.
Other information
It allows region administrators to manage objects in the region more efficiently and effectively. Especially when dealing with objects that impact the server performance so much that it will not let you return them.
The Disable Selected feature was working before fully but for some reason no longer has been working properly for quite some time now.
I have tried various conditions for an explanation on the issue:-
Residents object is in the land group.
Residents object is in another parcel.
Residents object is on the same parcel but not in the group.
Resident is not in the group with objects on the parcel.
My own objects on the same parcel not set to group.
My own objects set to group in another parcel.
Original Jira Fields
The text was updated successfully, but these errors were encountered: