Red Hat Bugzilla – Bug 153743
Contact Management online doc is incorrect; LDAP setup instructions are wrong
Last modified: 2007-11-30 17:07:17 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.6) Gecko/20050322 Galeon/1.3.20
Description of problem:
Help -> Evolution Contacts -> LDAP -> Configuring points to
Help -> Advanced -> Contact Management. The text here describes an assistant that doesn't exist. The Contacts -> New -> Contact List item is a single dialog that allows you to select names from an address book. It also doesn't include a way to configure an LDAP server as documented. The correct place to do that is Contacts -> New -> Address Book, which is also not an "assistant" but a two tab dialog in this case.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Navigate the online help to the indicated point
2. Compare the documentation to how the application operates.
3. Note disparity.
Actual Results: Documentation is incorrect
Expected Results: Documentation should give an accurate description of how to configure a new LDAP server. Correct documentation on creating a contact list should be provided, too.
Thanks for this bug report.
Yes, the 2.0 documentation is describing the old Evolution 1.4 (RHEL 3) way of
configuring LDAP addressbook access. I've checked and this mistake is still
present in the very latest documentation from upstream (Evolution 2.3). I've
filed this bug about the documentation upstream:
Created attachment 120825 [details]
Proposed patch to the documentation
(i) entirely removes the "config-prefs-contact" section (and references to it),
since the information there is either a poorly written duplicate of information
available elsewhere in the document, or is wrong
(ii) fills out the section on configuring LDAP with fresh information, based
upon how the dialog actually looks in RHEL4, whilst attemptint to stay true to
the style of markup in the rest of the documentation
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.