Da Group Edit Bug

I filed an in-game bug report on this, but wanted to provide more detail to make it clear what is happening.

I am in a group with a friend (Fey Brightwillow). She and I are both officers in the group. We did this so that we could work with and modify each other's objects easily (amongst other reasons).

On Thursday, we had created some objects in the Tehama sim. I had created several floor pieces and she had created several wall pieces. When we tried to edit each other's work (I do the alignment/precision work, she does the texturing/design work), we were unable to do so. Now let me be clear about this. I know (from David Linden, see below) that there is a group-edit texture bug, which would explain why she could not work with my floors. But I was unable to edit (move) her walls at all. She had to mark them for public edit for me to do so.

I checked the walls and they all were created by her and owned by her, the the group was our group (and we both only belong to that one group and no others, and no one else is in this group with us--just the two of us at the moment), so this was not the issue. I chalked it up to goofy SIM issues and we said we would try again tomorrow.

Friday comes and we still cannot do what we think we should be able to do. So we call David Linden over. He tries some things, has me add him to the group, still cannot. So he tells Fey to leave the group then for me to reinvite her. So we do that and now I can work with her walls. We also find she still cannot work with my floors, and David tells us there is a known group-edit-texture bug where you can look like you're doing it and make all the changes you want, but when you are done editing the object, it returns to it's prior textured stated. Ok, fine no biggie.

So Saturday we are just editing along happily when all of a sudden I am no longer able to work with her walls again. So we repeat the leave-group-reinvite thing and everything is back to normal. We edit and edit and edit, and it happens YET AGAIN! Same procedure cures the problem. I know it's not a huge, critical failure type thing, but it is annoying--especially when she is not on-line and I have work I want to be doing. Can someone look into this please?

Ok, new wrinkle. After removing and re-adding Fey to the group several times, I managed to accidentally leave the group myself and cannot create it with the same name. Is this an intended behavior or a bug?

Zan:

JinDokGhe and I experienced something VERY similar with the bugs you describe. I cannot answer your follow-up question about group names, but in hindsight I have to wonder if there isn't a more efficient way to remove/add someone to a group that you are in for the purpose of bug-avoidance.

Curiously...decaffienated,
Voodoo

It would be REALLY nice to hear something from a Linden on this one...even if it's "Yeah, we know, we're working on it, we don't know what's causing it". I'd be happy offer my assistance in helping to track it down.

There are two different issues here, so let's address them one at a time.

1. Something is broken in group permissions.

This is a high priority, and we should have a resolution by the next version. I apologize for the inconvenience it is causing you.

2. You left a group and cannot create one with the same name.

This is not as easy to resolve, because it is not just a simple error in the code. The problem stems from the fact that anyone can leave any of their groups. If that happens to be the last officer, the group can no longer be modified but it still exists. Then, when you attempt to make a group with the same name, that process fails because the group already exists. We have to support this functionality because people will be upset if they cannot leave a group and even more upset if a different group with the same name shows up in world. At some point in the future, we will put safeguards into the UI so that it at least verfies you really want to leave. For now, we have not scheduled a date for that feature.

Thank you Phoenix! That information is much appreciated. I know it is not the LL policy to comment on every bug or technical issue or feature request, but with this one in particular, which is REALLY frustrating and more and more frequent, it is nice to know that it is being dealt with. If there is any additional information that I can provide that would help track down the problem, I am happy to do so.