Toggle Alerts Log
Comment on [#5578] Turba contact lists could lose entries when switching share support on or off
Your Email Address
Enter the letters below:
__ __ _ ___ ___ ___ \ \ / / | / __| \| _ \ \ V / || \__ \ |) | _/ |_| \__/|___/___/|_|
>> 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?
Watch this ticket