Howdy all, this one's gonna sound trivial but I am quite curious.
I have been sending residents out to find cool builds to add to my website. Part of their job is to enter the "Type" listed for "Show in Find Places". There is a filter at the site that only lists the types that currently have any parcels under that "type", so one of the missing types in "Linden Location". I was a little shocked so I figured I'd try to find at least one build marked this way.
I opened "Search" and clicked the "Places" tab, then selected "Linden Location" from the drop-down. I typed in "linden" as the Find term and found seven matches. Trying just a few of them including "Governor Linden's Mansion, a Second Life heritage home" at "Clementina 188, 122, 62 (PG)" and "Luna Oaks Galleria" at "Luna 116, 98, 21 (PG)" (among others) each of these parcels are marked as "None", not "Linden Location". Is there any reason
1) They are marked as "None" insetad of "Linden Location"
2) They are returned in a search that is filtered to "Linden Location"
As a follow-up, I search for "Iris" and the Moth Temple, also marked as a "None" appeared. Does this mean that this search actually checks for Linden ownership of the parcel rather than the correct Find "type" selection only for "Linden Location"?
Just curious because I'm sure people would love to explore some of the Linden builds and areas which right now at least at my site have to be hunted for amongst the many other parcels set to "None".
Check the list yourself if you get a chance (you'll find Rausch and the Governor's Mansion correctly under the "None" type)...
http://slhandbook.com/parcelbrowse.asp
[ADDITIONAL INFORMATION]
Upon further checks I now notice the Find Places filter combo doesn't match the "About Land" Find categories list, specifically:
About Land: Stage doesn't exist in Search
Search: Store doesn't exist in About Land
The order of Search flip-flops the last two entries in addition to the error (Other, Store in Search; Stage, Other in About Land) as well as render the "&" as a ">". I will Bug report this as one error, though I'm guessing it's actually more than one!