Selling objects with Group Owned Land

I am trying to sell an object with a lot that is group owned. I build a single prim on the lot set it to mod/no copy/trans and deed the prim to group. Then I go to about land and set it to sell objects with land and hit show and it doesn's show my object. What am I missing here. Any help would be greatly appreciated.

I had this same problem, called live help, and nobody was ever able to figure it out. I was trying to sell houses I made with land for my group. It didn't work.

I'm waiting for one of my parcels to sell to see if the house on the lot actually changes ownership.

At least according to Torley it can't be done.

/invalid_link.html

I bug reported it a long time ago.

And it's not the only problem with the "sell objects with land" feature.

In some cases, linked objects can spontaneously unlink during the sale and the unlinked prims do not transfer. This can happen when the rotation of a linked object has been changed after it was linked.

I've also had problems with scripted prims not transfering when the permissions of the script were more restrictive than the permissions of the prim containing it. In these cases, I've been able to sell the prims in question with no problem, so it's not an issue of the permissions disallowing transfer.

Clearly, it needs some work. I sincerely hope that LL understands the importance of this feature working in all cases.

I'm really disappointed by the Linden response cited above. It's nice to know that it can't be done, but it would be better if there was an acknowledgement that it's a bug.

Thank you for the additional info Shack. I did not know about either of these additional problems.
It's Good to know. We can only hope that LL has this on there priority list.

This is a bug that's been around since at least last summer when the feature to "Sell all objects with land" was first introduced with 1.6.

Essentially, the checkbox will not work at all if the land is group owned. It is irrelevant whether the objects are deeded to group or not - they will not transfer to the new owner.

When the 1.7 preview was in play, I reported this behavior as a bug in hopes that it might be corrected in the new version.

The reply I received back on the Bug Report from Don Linden at the time was that this feature was "Working as Designed", and that this feature was not intended to work with group-owned land.

Hrmpf.

*sigh*

I guess this doesn't surprise me, but it does disappoint me.

At the very least, they should grey out that checkbox when the land is group-owned. There should be no room for confusion.

But something is very wrong with LL's requirements gathering process if they honestly think this is the way that we want it to work.

I'm not familiar with the previous history of this, so I'm glad you guys posted so I can learn more.

From my gut--just as someone who enjoys SL, this confuses me too, whether it's classified as a "bug" or "not", and should be under close examination during the upcoming groups improvements. That is my non-scientific feeling, and I am sorry for any disappointment I may have caused in this. This is not the only puzzling behavior with group-owned land: scripts not running for officers when "Outside Scripts" is unchecked is another.

In fairness - I went back through my e-mails tonight. It wasn't Don Linden, it was Dan Linden. And I was mistaken about him saying "Working as Designed". Its possible that was a result of an IM conversation, or its possible my brain is just like a sieve

Here's the email I received:

------------------------------

From: Dan Linden via RT <bugs@secondlife.com>
Date: Monday, October 03, 2005 5:28 PM
Subject: [rt.lindenlab.com #124340] Bug: E1 Preview V1.7.0.36 (Georgean) "Show" sell objects with land doesn't display group objects

"Sell objects with the land" only works for objects owned by people at
this time.

Dan

------------------------------

Add 2 more

1. Landing point overrides Teleport Home position for Officers if in the same sim.

2. Officers can not create prims in a no build parcel until they enable building.

Thanks for the clarification, Travis.

You know it's difficult to know how to approach LL sometimes. I mean, is it enough to make a bug report once or should we do it many times to get the point across?

I wouldn't be disappointed if we got back responses like "Obviously, we know that this is important, but other issues take precedence at this time." That's reasonable. But when bug reports fall into holes--I never even got a response back to mine on this issue--it causes concern.

When an issue like this arises, it should immediately be placed on a list of things to do. It's reasonable that it can't be done immediately, but there needs to at least be a process and an awareness that it needs to be done.