Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

1.12 BUG: Estate level land permissions

Ron Overdrive
Registered User
Join date: 10 Jul 2005
Posts: 1,002
08-03-2006 12:38
I have found that the No Fly and (more importantly) the Push Restriction permissions on an estate will reset themselves to disabled after opening the Estate Tools for the 2nd time since enabling those options regardless of the session. The No Fly isn't an issue but for those of us sim managers who deal with griefers on a regular basis it is crutial we have this permissions bug fixed because we can't afford to open up the Estate Tools to estate ban someone to have those options reset on us. This is a MAJOR bug.
Torley Linden
Enlightenment!
Join date: 15 Sep 2004
Posts: 16,530
08-07-2006 13:52
I'll investigate this as soon as I can--it sounds similar to something else I've been chasing. Thanx Ron.
_____________________
Ron Overdrive
Registered User
Join date: 10 Jul 2005
Posts: 1,002
08-07-2006 14:49
From: Torley Linden
I'll investigate this as soon as I can--it sounds similar to something else I've been chasing. Thanx Ron.


Your welcome Torely, I've already reported this directly to Beast Linden and gave a better worded report when I found it after filing the bug report. Basicly I first noticed this when I saw a parcel I was experienmenting claiming/deeding with didn't have the Restricted Push flag on, checked the estate, re-enabled it, and after looking for script time and physics time anomolies I saw the flag got reset again. So I began looking more closely at it and focused my attention on what I felt could be a major bug. Sure enough this affects all parcels in the region. Being that I'm only an estate manager for one sim in the preview I can't tell how far the bug spreads, being that its the Estate Tools affected by this bug I can only assume it affects all regions within the attached estate.
Torley Linden
Enlightenment!
Join date: 15 Sep 2004
Posts: 16,530
08-08-2006 13:13
[UPDATE] Checked with Beast, confirmed it's entered as a bug. Thanx again!
_____________________