[Tickets #3587] NEW: copy entry results in confusing notification

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=3587
-----------------------------------------------------------------------
 Ticket             | 3587
 Created By         | matthew.dunham at ic.ucsb.edu
 Summary            | copy entry results in confusing notification 
 Queue              | Turba
 Version            | 2.1
 State              | Unconfirmed
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
+New Attachment     | browse.php.patch
-----------------------------------------------------------------------


matthew.dunham at ic.ucsb.edu (2006-03-08 17:45) wrote:

i've got turba configured with two sources, one browseable/writeable
(localsql) and one non-browseable/readonly (ldap). my initial page is set to
browse.php. in this configuration, when i copy an entry from the ldap source
to the localsql source i get a warning that "Your default address book is
not browseable" warning followed by a blank screen.

this is confusing inasmuch as my "default" addressbook is the localsql one,
which is indeed browseable. but browse.php is defaulting to my ldap source,
presumably because that's the source from which the "copy entry"
originated.

i've attached a patch to make the notification somewhat more clear, although
this is arguably a bandaid.