-
Notifications
You must be signed in to change notification settings - Fork 0
[BUG-5656] llGiveInventory fails when no-copy items are given to attachments (even no-copy ones) #13603
Comments
Darien Caldwell commented at 2014-04-07T20:19:49Z Yes, this is expected behavior. LL had to tighten the permissions to disallow this due to it being used to get around permissions and copy content in bad faith. The workaround is for the attachment to be rezzed in the sim, not worn. |
Mo Noel commented at 2014-04-08T07:52:22Z Maybe scenario 2 you could argument as expected behaviour, but surely not scenario 1, where you transfer items with the exact same copy / transfer permissions and instead of transfering them, the system extinguishes them, so that the no copy property of the resident is actually lost. This is more severe then just breaking content, imho. |
Maestro Linden commented at 2014-04-08T22:51:57Z Hi Mo, thanks for the report. I can't seem to reproduce the content loss aspect of this issue.
It looks like the caveats list at https://wiki.secondlife.com/wiki/LlGiveInventory doesn't quite cover this case (giving a no-copy item to a no-copy attachment). I think allowing this transfer would be 'safe', since the attachment and transferred item have the same copy and transfer permissions, but I want to check with other Lindens to see if this would be reasonable to support. |
Mo Noel commented at 2014-04-09T23:24:56Z I was pretty sure the items vanished, actually two times while I tested. I still found the empty box in the inventory. But right now I am not able to reproduce the vanishing either. The items stay in the inventory of the box. So, either it was some temporary event, or I my observation has an error (e.g. I mixed some test cases). However. it would be nice and but consistant, if the transfer of no copy, transfer -items would work. ;) |
Maestro Linden commented at 2014-04-10T17:22:30Z We checked the code and found that this error message will always trigger when the item is no-copy and the target object is an attachment. The server code could be smarter about this, and allow the operation if the attachment was already no-copy with its folded permissions. For the time being, I've added this behavior to the list of documented caveats: |
Steps to Reproduce
Have an attachment, set permissions to transfer no copy, modify and have a script inside, that is no copy, transfer, no modify. Give it away.
Have an scripted add on installer that tries to give add-on-items with llGiveInventory to the attachment.
Have the add-on-items inside the installer (notecards, animations) have the permissions no copy and transfer (same as the attachment),
Give it away to the same other resident like before.
Have the resident wear the attachment and rez the installer
Run the install and you get the error "Blocked by permissions" and the no copy add-on-items from the install-box are gone with the wind. The installer is empty, the attachment did not get the items.
-> this deletes residents items.
Workaround is:
and
==
2nd Scenario
-> it gets the error "Destination did not accept"
However, I am thinking this did work very well, before and but rendered the attachemt to no copy, no transfer
Actual Behavior
llGiveInventory fails either with Blocked by permissions or Destination did not accept
no copy items of the resident get stolen by the system.
Expected Behavior
no error,
items transfer fine
items get not stolen from the resident
Other information
Seems related to SCR-491
Original Jira Fields
The text was updated successfully, but these errors were encountered: