6.0.0-beta1
7/11/25

[#3587] copy entry results in confusing notification
Summary copy entry results in confusing notification
Queue Turba
Queue Version 2.1
Type Bug
State Resolved
Priority 1. Low
Owners
Requester matthew.dunham (at) ic (dot) ucsb (dot) edu
Created 03/09/2006 (7064 days ago)
Due
Updated 03/10/2006 (7063 days ago)
Assigned
Resolved 03/10/2006 (7063 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
03/10/2006 12:00:47 AM Jan Schneider Comment #2
State ⇒ Resolved
Reply to this comment
Fixed in CVS.
03/09/2006 01:45:42 AM matthew (dot) dunham (at) ic (dot) ucsb (dot) edu Comment #1
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ copy entry results in confusing notification
Queue ⇒ Turba
New Attachment: browse.php.patch Download
Reply to this comment
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.










Saved Queries