[#MISC-543] loss of transfer rights on self created objects

4. Second Life Misc Issues - MISC

loss of transfer rights on self created objects

Created: 06/Aug/07 03:37 PM Updated: 26/Jun/09 12:14 PM

Component/s:

Miscellaneous

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

File Attachments:

None

Image Attachments:

1. 1 prim, no contents.JPG
(419 kB)

Environment:

« Hide

not applicable as problem is inworld..... clear cache did not fix....

Issue Links:

Relates

This issue Relates to:

SVC-2621 Meta-Issue: New/modified permissions

Source Version:

Description

« Hide

i lost transfer rights for an object created by me.... i did attach an object not made by me to it at one point.... but when i unlink the 3rd party object..... all except one prim has lost transfer rights, i am not entirely sure when this bug may have first appeared so the single prim that still has all rights may have been added after

there are scripts in the prims..... i checked them they are fine, full perms, removed them anyway...no change

the 3rd party object i linked to it.....the prim itself was modify,copy,no transfer.... the scripts in it were mod,no copy,no transfer

strange thing is.... the rights i have on the object are the same as the 3rd party prim, and i never made the 3rd party object the root prim
example in picture attachment

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Lex Neva added a comment - 07/Aug/07 09:35 AM

If you linked your object to a no-transfer prim, the entire link set will be no-transfer.

[ Permlink | « Hide ]

Aquarius Paravane added a comment - 14/Dec/07 04:31 PM

This is quite unacceptable.

All very well while the linkset is linked, but when it's unlinked again, the prims that I created and I own and contain no scripts should be full rights to me.

This is an enormous waste of time and has left me with no option but to unlink, analyse and partially rebuild houses that I made for transfer.

It happened to me once when I linked in a TP ball that I forgot was no transfer.

It's happened again, this time it's a no transfer script that was in the prims and was removed. But too late, it poisoned the prims and the poison spreads each time I link.

Suggestions:

1) Child prims should retain their individual rights through link and unlink without getting contaminated by the rights of other prims in the linkset.
2) If I own a prim and I created it, it should be full rights to me at all times.
3) If I own a prim and I created it, and the rights get messed up, it should be possible for me to fix the rights.

[ Permlink | « Hide ]

Alexa Linden added a comment - 08/Feb/08 03:49 PM

Is anyone still experiencing this problem?

[ Permlink | « Hide ]

Sonata Nayar added a comment - 26/Jun/09 10:51 AM

I am. And my build was made from scratch, each prim made by me, all the scripts by me, and the textures full perm.