• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: SVC-141
Type: Bug Bug
Status: Reopened Reopened
Priority: Normal Normal
Assignee: Unassigned
Reporter: Lex Neva
Votes: 7
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
2. Second Life Service - SVC

Restrict Pushing disallows pushes from objects set to group

Created: 26/Apr/07 06:34 PM   Updated: 12/Aug/08 08:29 PM
Return to search
Component/s: Groups, Physics
Affects Version/s: None
Fix Version/s: None

Issue Links:
Relates

Linden Lab Issue ID: DEV-4266


 Description  « Hide
The Restrict Pushing option was, if I recall correctly, originally designed to allow pushing in certain circumstances even when pushing is restricted. For individual-owned land, objects owned by the land-owner were allowed to use llPushObject() on people who are on the parcel. For group-owned land, objects SET to the group and owned by an officer were allowed to use llPushObject().

Several updates after push restriction was enacted, suddenly objects owned by officers and set to the group that owns the land were unable to successfully use llPushObject(). I reported this bug then, and it appears that it still has not been fixed. The only solution is to deed the object to the group, which can often be a sub-optimal solution.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Harleen Gretzky added a comment - 22/Oct/07 04:33 PM
Is this still an issue? I could not reproduce it, objects owned by me on group land where I am an officer of the group still push avatars.

[ Permlink | « Hide ]
Lex Neva added a comment - 22/Oct/07 05:54 PM
Did you test this with the object owned by you and pushing you? That seems to work for me... but objects owned by me on land owned by a group that I'm an officer in still can't push other people.

lindenrobot made changes - 23/Oct/07 03:29 PM
Field Original Value New Value
Linden Lab Issue ID DEV-4266
[ Permlink | « Hide ]
Harleen Gretzky added a comment - 23/Oct/07 11:44 PM
You are correct, works for me, but not others,

aric linden made changes - 25/Oct/07 03:49 PM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Won't Finish [ 2 ]
[ Permlink | « Hide ]
Lex Neva added a comment - 25/Oct/07 03:51 PM
I'd really like to know why this was resolved won't finish. I'm pretty sure that the current functionality goes against the spec LL originally published for push restriction.

Rob Linden made changes - 22/Dec/07 01:26 AM
Workflow jira [ 11061 ] jira-2007-12-21 [ 22058 ]
Rob Linden made changes - 23/Dec/07 12:25 AM
Workflow jira-2007-12-21 [ 22058 ] jira-2007-12-22a [ 48816 ]
[ Permlink | « Hide ]
Kitto Flora added a comment - 29/Feb/08 11:34 AM
This is indeed still a problem as of February 29 '08 in both Havok1 and Havok4. It is entirely and consistently reproducible.

BUG: A scripted object set to the same group as the land it is in fails to llPushObject() a 3rd-party Avatar when the land is set to no-push.

This bug breaks content when officers of the land rez vehicles, toys etc. that work fine in other circumstances.


Kitto Flora made changes - 29/Feb/08 11:34 AM
Resolution Won't Finish [ 2 ]
Status Resolved [ 5 ] Reopened [ 4 ]
[ Permlink | « Hide ]
Keiko Rau added a comment - 02/Apr/08 06:24 PM
I have one of Kitto's monorail's, and as of the update to Havok 4, it no longer pushes the avatar up and out of the car when they stand up. They end up getting stuck inside the car. Its on group land, and im an owner. This was not the case with Havok 1, where it worked properly. Perhaps this is new behaviour that should be reported as a H4 issue (in that its not doing something the same as H1 did it), but I thought here was a good place to start.

Keiko Rau made changes - 02/Apr/08 06:33 PM
Link This issue is related to by SVC-1968 [ SVC-1968 ]
Keiko Rau made changes - 02/Apr/08 06:39 PM
Link This issue is related to by SVC-875 [ SVC-875 ]
Keiko Rau made changes - 02/Apr/08 06:47 PM
Link This issue duplicates SVC-1179 [ SVC-1179 ]
Keiko Rau made changes - 02/Apr/08 06:48 PM
Link This issue duplicates SVC-1179 [ SVC-1179 ]
Keiko Rau made changes - 02/Apr/08 06:48 PM
Link This issue Relates to SVC-1179 [ SVC-1179 ]
[ Permlink | « Hide ]
Keiko Rau added a comment - 02/Apr/08 09:37 PM
I had a chance to talk to Kitto about this and he seems well informed on the various aspects of the issue. After talking to him, I now understand that what I am seeing is two seperate issues... the permission problem reported in this Jira, and additionally, the differences that I have experienced with Havoc 4. I'll follow those up in a more appropriate Jira. I just didnt want this one getting lost amongst my confusion.

[ Permlink | « Hide ]
Argent Stonecutter added a comment - 24/May/08 12:18 PM
I would like to see some Linden feedback here. The current behavior is consistent, but it doesn't match the way the restriction was initially specced, and there has been no explanation.

[ Permlink | « Hide ]
Lex Neva added a comment - 24/May/08 12:22 PM
I would, too. Not only was it originally specced to allow group officers, that's the way it worked for the first few releases.

McCabe Maxsted made changes - 12/Aug/08 08:27 PM
Component/s Groups [ 10222 ]
McCabe Maxsted made changes - 12/Aug/08 08:29 PM
Component/s Physics [ 10038 ]
Sue Linden made changes - 13/Nov/08 12:07 PM
Workflow jira-2007-12-22a [ 48816 ] jira-2008-11-14 [ 81576 ]
Sue Linden made changes - 13/Nov/08 04:35 PM
Workflow jira-2008-11-14 [ 81576 ] jira-2008-11-14a [ 88537 ]

Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators