6.0.0-git
2019-05-20

[#3271] Show list of available client address book choices on config screen
Summary Show list of available client address book choices on config screen
Queue Turba
Queue Version Git master
Type Enhancement
State Resolved
Priority 1. Low
Owners mrubinsk (at) horde (dot) org
Requester ccarlin (at) physics (dot) tamu (dot) edu
Created 2006-01-15 (4873 days ago)
Due
Updated 2010-10-01 (3153 days ago)
Assigned 2006-02-13 (4844 days ago)
Resolved 2010-07-08 (3238 days ago)
Milestone 3
Patch No

History
2010-10-01 08:36:46 d-fens (at) 00010111 (dot) de Comment #13 Reply to this comment
still have problems with an empty but required dropdown in the 
configuration dialog for turba:
Name of client addressbook is empty but required, how do i fix this?
2010-07-08 22:08:01 Michael Rubinsky State ⇒ Resolved
 
2010-07-08 22:07:46 Git Commit Comment #12 Reply to this comment
Changes have been made in Git for this ticket:

Make use of the configspecial we have for contact sources.
Re-add this now that we are working towards Horde 4
(Finally) closes Bug: 3271

http://git.horde.org/diff.php/turba/config/conf.xml?rt=horde-git&r1=c31211fd5cee20c7fe88e3517d6be96a361f6168&r2=898c9178ce8a81ebff27112895734a1c479cbdb4
2009-08-02 13:28:35 Michael Rubinsky Version ⇒ Git master
 
2008-11-09 16:29:03 Chuck Hagenbuch State ⇒ Accepted
 
2008-11-06 02:54:43 Chuck Hagenbuch State ⇒ Stalled
 
2008-10-08 14:02:52 Michael Rubinsky Summary ⇒ Show list of available client address book choices on config screen
 
2008-10-08 14:01:40 Michael Rubinsky Comment #11 Reply to this comment
It's possible to set the value manually, but it's not possible in a BC 
way to provide a list of available sources on the config screen since 
it would need a new configspecial tag.
2008-10-08 13:11:15 Jan Schneider Milestone ⇒ 3
 
2008-10-08 13:10:36 Jan Schneider Comment #10
State ⇒ Feedback
Reply to this comment
Isn't this possible meanwhile?
2006-12-14 21:35:02 Michael Rubinsky Comment #9
State ⇒ Stalled
Reply to this comment
Stalling until Horde 4
2006-02-13 02:17:37 Chuck Hagenbuch Type ⇒ Enhancement
State ⇒ Assigned
Priority ⇒ 1. Low
 
2006-02-13 01:01:13 Michael Rubinsky Comment #8
State ⇒ Feedback
Reply to this comment
Reverted in HEAD.  It wasn't BC, as Turba 2.2 would now require Horde 3.2...



While were at it, this isn't really a bug ticket, but an enhancement 
request to list available sources in the setup screen.  Can someone 
update this or shoud I create a new ticket?


2006-02-12 23:03:31 Michael Rubinsky Comment #7
State ⇒ Resolved
Reply to this comment
Implemented in HEAD.
2006-02-01 04:07:50 Michael Rubinsky Comment #6
State ⇒ Stalled
Priority ⇒ 1. Low
Reply to this comment
Stalling until Bug: 3304 is resolved.
2006-01-16 15:05:22 Michael Rubinsky Comment #5 Reply to this comment
I don't think we need a bc way, because Hermes is not yet released.
We could add a configspecial tag that retrieves its enum values from
an API call.
WIll do. Thanks.
2006-01-16 08:56:48 Jan Schneider Comment #4 Reply to this comment
Any input on a way to better handle this in a BC way would be welcome...
I don't think we need a bc way, because Hermes is not yet released. We 
could add a configspecial tag that retrieves its enum values from an 
API call.
2006-01-16 05:56:23 ccarlin (at) physics (dot) tamu (dot) edu Comment #3 Reply to this comment
The shared addressbooks work as per your instructions.
2006-01-16 05:14:13 Michael Rubinsky Comment #2 Reply to this comment
The code for client address books uses the key into $cfgSources.  The 
'name' given a shared address book is only the display name and is 
stored in the share.



Currently, for this to work, you would need to enter the internal name 
of the source into the client address book field.  The internal name 
is something like the following:



localsql:ad60cc4ce7102b3aac2420aedbc664c1



where localsql is obviously the source the shared address book is 
based on and the second part is the unique identifier for the share.   
You can find this value by looking in the datatree area of the 
administration section of the user interface.



Any input on a way to better handle this in a BC way would be welcome...


2006-01-15 02:03:52 Chuck Hagenbuch Assigned to Michael Rubinsky
State ⇒ Assigned
 
2006-01-15 00:46:18 ccarlin (at) physics (dot) tamu (dot) edu Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ Cannot set client addressbook to a shared book
Queue ⇒ Turba
Reply to this comment
I'm trying to use hermes (cvs pulled 1-13) and turba (cvs pulled 
1-13), which is using shared addressbooks but I keep running into the 
"no clients" error in hermes. I can see the clients in the turba 
addressbook.



In sources.php I specified a shared backend called localsql, and 
specified that as the "name of source for creating new shares." I then 
created a shared addressbook called c2 and populated it with a few 
clients. I can see the clients fine from my account and from other 
accounts, and have no problems with addressbook sharing.



I then set c2 as the "Name of client addressbook", but hermes shows no 
clients available.

Saved Queries