[Tickets #5578] Re: Turba contact lists could lose entries when switching share support on or off

bugs at bugs.horde.org bugs at bugs.horde.org
Fri Aug 24 20:15:42 UTC 2007


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

Ticket URL: http://dev.horde.org/horde/whups/ticket/?id=5578
-----------------------------------------------------------------------
 Ticket             | 5578
 Updated By         | Michael Rubinsky <mrubinsk at horde.org>
 Summary            | Turba contact lists could lose entries when switching share support on
                    | or off
 Queue              | Turba
 Version            | HEAD
 Type               | Bug
-State              | Assigned
+State              | Feedback
 Priority           | 1. Low
 Owners             | Michael Rubinsky
-----------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2007-08-24 13:15) wrote:

> This could also happen, however, when upgrading to Turba 2.2 when the 
> flatten shares upgrade script is run since this could also change the 
> $cfgSource array keys as well.  Fixing this in the upgrade script is 
> not possible for all sources since we would run into authentication 
> issues with some backends.  We would have to build in some sort of 
> maintenance in Turba to  run a conversion, although I haven't looked 
> deeply enough at this yet to know if it is 100% possible or not....

This part of the issue has been resolved with the addition of the
upgradelists maintenance task.  

I'm still torn about the first part of the issue, although I'm leaning
towards saying that it *is* a change in sources, so we can accept those
contacts disappearing from lists in other sources.  While writing a
maintenance task to update them would be trivial, it would either requrie a
new pref to be added any time a source is switched or a hard coded check
for some sort of configuration flag that would have to be checked EVERY
login.  Seeing how these 'foreign contacts` were not even working properly
in 2.1.4 (or maybe earlier), I say just document this somewhere...thoughts?



More information about the bugs mailing list