6.0.0-beta1
8/14/25

[#4397] When adding New Contacts, read-only LDAP address books should not be available
Summary When adding New Contacts, read-only LDAP address books should not be available
Queue Turba
Queue Version 2.1
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester ditsa (at) ccf (dot) auth (dot) gr
Created 09/08/2006 (6915 days ago)
Due
Updated 09/22/2006 (6901 days ago)
Assigned
Resolved 09/08/2006 (6915 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
09/22/2006 01:19:40 PM ditsa (at) ccf (dot) auth (dot) gr Comment #3 Reply to this comment

[Show Quoted Text - 11 lines]
It works

Thank you for your help


09/08/2006 02:34:16 PM Michael Rubinsky Comment #2
State ⇒ Not A Bug
Reply to this comment
There used to be an option in turba/config/sources.php to make an
address book as read-only. Has this option become obsolete? Is there
a way to prevent this?
Use the permissions system. (Administration -> Permissions)


09/08/2006 09:42:36 AM ditsa (at) ccf (dot) auth (dot) gr Comment #1
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ When adding New Contacts, read-only LDAP address books should not be available
Queue ⇒ Turba
Reply to this comment
We have configured two addressbooks (mysql and ldap).  The ldap 
addressbook in turba/config/sources.php is defined as non-browsable 
and non-exportable, but can not be defined as non-writeable, to 
indicate that you can not Add a New Contact there. As a result, the 
LDAP address book appears in the list of AddressBooks to add entries to.



There used to be an option in turba/config/sources.php to make an 
address book as read-only. Has this option become obsolete? Is there a 
way to prevent this?


Saved Queries