[Tickets #12329] Re: Many fields are ignored when importing vCard files

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12329
------------------------------------------------------------------------------
  Ticket             | 12329
  Updated By         | spam at ancow.no-ip.org
  Summary            | Many fields are ignored when importing vCard files
  Queue              | Turba
  Version            | 4.1.0
  Type               | Bug
  State              | Resolved
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Jan Schneider
------------------------------------------------------------------------------


spam at ancow.no-ip.org (2013-08-16 13:48) wrote:

This bug isn't resolved and shouldn't be marked as such.

>> The biggest problem in my opinion is that these values are moved to
>> /dev/null without ANY notice to the user.
>>
>> The user should be informed that his/her data is trashed or should be
>> given some way of resolving this issue.
>
> How should that work? You cannot display a confirmation button  
> during synchronization.

In the short term, until this is properly fixed, you should abort the  
synchronisation to prevent data loss. This is not just the correct  
behaviour, this would also point the user to the problem rather than  
making them have to debug where exactly their data is discarded.


One way to prevent data loss would be to provide an extra field in the  
storage backend that would simply hold all the data turba doesn't know.
Another would be what seemingly every other program I've used for  
synchronisation so far does: store the incoming vCard separately,  
update the recognised fields right before syncing and simply send that  
vCard during sync.
Finally, you could simply operate solely on vCards. While this is  
probably slower, it would avoid the problem of not being able to store  
unknown data completely. And you could always cache the recognised  
fields in the database, reducing the performance hit.