| Summary | Amend in-code documentation in /turba/config/sources.php |
| Queue | Turba |
| Queue Version | 2.1.3 |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | Horde Developers (at) |
| Requester | Otto.Stolz (at) uni-konstanz (dot) de |
| Created | 12/06/2006 (6821 days ago) |
| Due | |
| Updated | 06/14/2007 (6631 days ago) |
| Assigned | 12/08/2006 (6819 days ago) |
| Resolved | 06/14/2007 (6631 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Assigned to
State ⇒ Assigned
Can one of the LDAP gurus please check that I got the dn and
objectclass settings correct?
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Amend in-code documentation in /turba/config/sources.php
Queue ⇒ Turba
New Attachment: sources.php.delta
State ⇒ Unconfirmed
available documentation on configurating addressbook sources. Hence,
it should comprise the information required to adapt the configuration
to existing addressbook servers.
In particular:
- all relevant special params settings should be discussed,
- the possible Turba attributes should be discussed.
Please amend my attached proposal at the places marked by double
question marks.
Apparently, the term "standard Turba attributes' has been used
inconsistently. My attached proposal uses this term only for the
attributes starting with underscores; it uses the term "Turba
attributes" for the union of the standard Turba attributes and the
attributes defined in turba/config/attributes.php.