|
Bri Hasp
Registered User
Join date: 13 May 2005
Posts: 18
|
03-13-2007 22:17
I just suffered what I think is a bizarre permissions operation. Curious if it is one of those ‘deadly sins’ or has a purpose?
We were working on a new script that resides in a simple box prim. Took it to inventory to move to the next test phase. After the take, it changed to no copy /no modify to me. Hence is lost forever.. Regrettably we didn’t get to an external backup in the heat of battle.
We were Creator / Owner of the script and the prim…
How can I assure myself of this never happening again?
|
|
Anti Antonelli
Deranged Toymaker
Join date: 25 Apr 2006
Posts: 1,091
|
03-14-2007 01:45
Who is "we"? "We" cannot be the creator of an object, an object only has one creator and that person has control over the perms. If you picked up a shared object, and you were not the creator, then unless the creator specifically set the permissions ahead of time to allow copy and modify to the next owner then permissions are behaving just like they should. It might not be convenient when working with partners (or alt accounts for that matter) but that's the way it's supposed to work.
If you want to work on shared projects, you need to be very careful that the creator of each object (and particularly scripts) sets perms ahead of time, or better yet only take copies and not the original, and both of you take a copy while you're at it.
|
|
Zephy Toshihiko
Registered User
Join date: 3 Dec 2006
Posts: 12
|
03-14-2007 07:10
Have you checked to see you really can't edit it now. I have seen it when an object I created and then took back to Inventory showed no modify, but when I rezzed it again I could edit it.
|
|
Winter Ventura
Eclectic Randomness
Join date: 18 Jul 2006
Posts: 2,579
|
03-14-2007 08:01
yeah, a simple "shift slide" (clone action) can result in a permanently locked prim. shared projects are both complicated to execute without running afoul of the permissions system... and dangerous.
if your copy is no longer viable.. check with your friend.
Of course.. since it's housed in an "Object" your friend may have a great deal of hunting to do, to find his last copy of the project.
Rez it on the ground, and have "we" look at the various parts. I've had some weird experiences with my friends modding and/or creating scripts inside objects owned by me. So you may want to re-drop the prim, and see if your friends can untangle the permissions on their own scripts.
_____________________
 ● Inworld Store: http://slurl.eclectic-randomness.com ● Website: http://www.eclectic-randomness.com ● Twitter: @WinterVentura
|
|
Bri Hasp
Registered User
Join date: 13 May 2005
Posts: 18
|
Bad Grammer
03-14-2007 10:09
What I should have typed
I am the sole creator/owner of the script and the prim.
This was not a shared project, which I can see can could possible problems.
I tried rez'n the prim again... no change..while update is on I will create a hot key to Crimson and NEVER trust the editor and asset inventory again.
Thanks for the suggestions, if I ever do a joint project…
|