Closed
Bug 85807
Opened 24 years ago
Closed 24 years ago
Subtree scope got offset in the First added Directory server
Categories
(SeaMonkey :: MailNews: Address Book & Contacts, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: yulian, Assigned: srilatha)
Details
2001061304 winds build
With new profile to start Browser
1. bring up Addressing Preferences window
2. Check the box for "Directory Server"
3. Click "Edit Directories" button
4. In "LDAP Directory Servers" window, click Add
5. Fill out "Name" and Hostname" text box in
"Directory Server Properties" window
6. click OK to dismiss "Directory Server Properties" window
7. select the server you just added and click Edit
8. Click Advanced tab in the "Directory Server Properties" window
9. you see Subtree is chosen as the default Scope
10. click Ok to dismiss "Directory Server Properties" window
11. Click OK to dismiss "LDAP DIrectory Servers" window
12. In Preferences window, click Edit Directory button to
bring up :LDAP Directory Servers" window again
13. repeat setp 7&8
14. notice the Subtree scope doesn't hold any more
This problem only happens to the first added server on all platforms.
Comment 1•24 years ago
|
||
I assume it's related, but I noticed myself that when setting up the first LDAP
server for a new profile, the "default" scope is set to "0" (BASE). Unless I
manually go into the Advanced tab, and manually click on "SUBTREE", it stays
"BASE".
This is pretty serious, I think this is why people in IS had problems getting
LDAP Autocomplete to work. And, I think a lot of users will get trapped in this
as well, it's not obvious that you have to go into "Advanced" settings to even
get anything to work (a scope of "BASE" is almost never gonna find anything)
-- Leif
Assignee | ||
Comment 2•24 years ago
|
||
Marking this resolved fixed since this has been fixed with the checkin for bug
79252
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•24 years ago
|
||
Verified with 2001070306 0.9.2 wins build
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•