
| Key: |
VWR-2811
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Won't Finish
|
| Priority: |
Normal
|
| Assignee: |
Unassigned
|
| Reporter: |
davie zinner
|
| Votes: |
7
|
| Watchers: |
3
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Duplicate
|
|
|
|
This issue is original of duplicate:
|
|
|
VWR-3071 Objects Set for Sale should not default to "Show in Search"
|
|
|
|
|
Relates
|
|
This issue Relates to:
|
|
VWR-2908
Sale Item Search should not list certain kinds of items.
|
|
|
|
|
|
This issue is related to by:
|
|
|
VWR-3071 Objects Set for Sale should not default to "Show in Search"
|
|
|
|
|
|
|
| Linden Lab Issue ID: |
DEV-4262
|
Marking an object for sale should NOT imply an open invitation for the general population to teleport to the location of that object.
It is common to define a default landing point for your parcel where you want to encourage visitors to arrive, and it's common also to have bedrooms and workshops on the same parcel where you do NOT want to encourage visitors to teleport to directly. With this new policy, the only way to prevent the general public from teleporting into bedrooms or workshops is to examine every object on your parcel, looking for ones marked for sale, then choosing to leave it, move it, delete it, or uncheck the for-sale checkbox. This is unreasonable for, say, a 32K sq.m. parcel with 7500 objects, or a sim-size parcel with 15000 objects. The workarounds are not pleasant – either slice and dice parcels into many smaller ones to make finer-grained search settings, or install security devices to eject the people you send into our bedrooms and workshops.
Just as permissions on new objects start out restrictive, so should the search settings. When an object creator makes a new object, s/he can choose to distribute the object – or publish its location – but neither should happen automatically by default.
|
|
Description
|
Marking an object for sale should NOT imply an open invitation for the general population to teleport to the location of that object.
It is common to define a default landing point for your parcel where you want to encourage visitors to arrive, and it's common also to have bedrooms and workshops on the same parcel where you do NOT want to encourage visitors to teleport to directly. With this new policy, the only way to prevent the general public from teleporting into bedrooms or workshops is to examine every object on your parcel, looking for ones marked for sale, then choosing to leave it, move it, delete it, or uncheck the for-sale checkbox. This is unreasonable for, say, a 32K sq.m. parcel with 7500 objects, or a sim-size parcel with 15000 objects. The workarounds are not pleasant – either slice and dice parcels into many smaller ones to make finer-grained search settings, or install security devices to eject the people you send into our bedrooms and workshops.
Just as permissions on new objects start out restrictive, so should the search settings. When an object creator makes a new object, s/he can choose to distribute the object – or publish its location – but neither should happen automatically by default. |
Show » |
made changes - 19/Oct/07 05:16 PM
| Field |
Original Value |
New Value |
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
|
Fix Version/s
|
|
1.18.4 Release Candidate
[ 10180
]
|
made changes - 19/Oct/07 05:46 PM
|
Status
|
Resolved
[ 5
]
|
Reopened
[ 4
]
|
|
Resolution
|
Fixed
[ 1
]
|
|
made changes - 23/Oct/07 03:18 PM
|
Linden Lab Issue ID
|
|
DEV-4262
|
made changes - 23/Oct/07 04:39 PM
|
Resolution
|
|
Won't Finish
[ 2
]
|
|
Status
|
Reopened
[ 4
]
|
Resolved
[ 5
]
|
made changes - 26/Oct/07 03:38 AM
|
Resolution
|
Won't Finish
[ 2
]
|
|
|
Status
|
Resolved
[ 5
]
|
Reopened
[ 4
]
|
made changes - 29/Oct/07 11:16 AM
|
Status
|
Reopened
[ 4
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Won't Finish
[ 2
]
|
made changes - 29/Oct/07 11:21 AM
|
Link
|
|
This issue Relates to VWR-2908
[ VWR-2908
]
|
made changes - 29/Oct/07 07:13 PM
|
Resolution
|
Won't Finish
[ 2
]
|
|
|
Status
|
Resolved
[ 5
]
|
Reopened
[ 4
]
|
made changes - 06/Nov/07 08:50 PM
|
Status
|
Reopened
[ 4
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Won't Finish
[ 2
]
|
made changes - 14/Nov/07 06:39 AM
|
Link
|
|
This issue is related to by VWR-3071
[ VWR-3071
]
|
made changes - 18/Nov/07 01:08 PM
|
Link
|
|
This issue is duplicated by VWR-3071
[ VWR-3071
]
|
made changes - 22/Dec/07 03:09 AM
|
Workflow
|
jira
[ 16080
]
|
jira-2007-12-21
[ 28017
]
|
made changes - 22/Dec/07 03:20 AM
|
Workflow
|
jira
[ 28017
]
|
jira-2007-12-21
[ 28660
]
|
made changes - 22/Dec/07 03:52 PM
|
Workflow
|
jira-2007-12-21
[ 28660
]
|
jira-2007-12-22
[ 35001
]
|
made changes - 22/Dec/07 10:44 PM
|
Workflow
|
jira-2007-12-22
[ 35001
]
|
jira-2007-12-22a
[ 46168
]
|
made changes - 22/Dec/07 11:10 PM
|
Workflow
|
jira-2007-12-22
[ 46168
]
|
jira-2007-12-22a
[ 47516
]
|
made changes - 13/Nov/08 11:14 AM
|
Workflow
|
jira-2007-12-22a
[ 47516
]
|
jira-2008-11-14
[ 66461
]
|
made changes - 13/Nov/08 11:48 AM
|
Workflow
|
jira-2007-12-22a
[ 66461
]
|
jira-2008-11-14
[ 77242
]
|
made changes - 13/Nov/08 05:20 PM
|
Workflow
|
jira-2008-11-14
[ 77242
]
|
jira-2008-11-14a
[ 104476
]
|
made changes - 13/Nov/08 05:39 PM
|
Workflow
|
jira-2008-11-14
[ 104476
]
|
jira-2008-11-14a
[ 111821
]
|
made changes - 13/Nov/08 05:54 PM
|
Workflow
|
jira-2008-11-14
[ 111821
]
|
jira-2008-11-14a
[ 116727
]
|
made changes - 13/Nov/08 06:14 PM
|
Workflow
|
jira-2008-11-14
[ 116727
]
|
jira-2008-11-14a
[ 123956
]
|
made changes - 13/Nov/08 06:50 PM
|
Workflow
|
jira-2008-11-14
[ 123956
]
|
jira-2008-11-14a
[ 137576
]
|
|