|
|
|
The problem formed in two stages, a while back it used to be that temp objects highlighted but did not get returned on arbitrary owner selections.
I'm seeing this problem in the Linux client. I'm not sure this is critical though, it can be worked around.
I deeded now the land to my group and now with every entry from: set to group, owned by parcel owner, etc. the temporary waves show up,too.
This came up @ http://wiki.secondlife.com/wiki/Bug_triage/UI_Agenda
Changed priority, importing for further investigation, will ask Spike about this too. Actually, since this issue allows transfer of "no transfer" objects, I changed it back to critical...
ok, the original post states that
"the Temp objects are returned to the person specified, even if owned by the land owner. " I cannot get that to happen with "Smartwaves 2" waves, which are "no transfer", and what the original post refered to. can anyone else transfer "no transfer" objects this way? changing priority back to major This has always been the case as far back as I can remember, but it never returns the objects to the other avatar. It does kill the temp-on-rez objects, if you are using a rezzor you can simply wait for the next cycle to occur the new temp-on-rez objects will not be highlighted. Tested this with another avatar, did not matter the permissions of the temp-on-rez object it was never transfered to teh other avatar.
Actually that is right that the objects aren't sent to the other av, but it is annoying though that they go away. I mean the ownership should be followed.
This issue went internal triage, and was investigated. "Won't Finish", because: "This is due to temp objects always being returned whenever anything is returned in a parcel. We are displaying the items that are about to be returned, thus confusing people into thinking that the temp objects are owned by everyone."
Except the temp prims are not returned to anybody, the title is misleading, temp prims are simply killed by this action. So why are temp prims being selected for return in the first place?
This makes no sense. Why should temp objects be returned when anything else is? They have their own short lifetimes to live out.
I just had this happen to me, so tested it with an alt, the temp items are created and owned by me, so they are full perms, when I do the return objects via the land options, I then checked the alt, and she only had her one object, even though it looked like all items were sent when I clicked the return
I think it just kills off the temp objects, just not sure why also hard to pinpoint a specific object when it selects temp objects as well, so it would be nice to see this fixed. Voted for it! In addition to the bug with blank names I crash now when returning objects from somebody
 this problem is getting a pretty serious issue for me, as i use a temp rezzer for the karts people use on my track, its impossible for me to return any items to there owners when there are people driving because it will immediately delete all karts. so i end up searching the whole region for prims i see in my object list, so i can directly select and return them, or wait until no one is driving.....
i also have this issue it would also seem those temp objects do not go to the correct owner if you do have to use return objects to return prims you cant find any were while the temp objects do come back eventually whose to say who got or didn't get the objects that were returned when they were not suppose to be returned
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Reopened
Normal
About Land - Objects: Temp objects are owned by everybody and returned to everybody.
1. Rez some prims on your land as "temporary on rez".
2. Open up "About Land".
3. Click "refresh list".
4. Select any object owner from the list.
5. Return their objects.
Expected results:
Only objects owned by the selected person (temporary or not) should be hilighted and returned.