[Tickets #2530] RESOLVED: Importing vCal saves to wrong calendar

[bugs@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=2530
-----------------------------------------------------------------------
 Ticket             | 2530
 Updated By         | horde at nps.parcellsharp.net
 Summary            | Importing vCal saves to wrong calendar
 Queue              | Kronolith
 Version            | HEAD
 State              | Bogus
 Priority           | 2. Medium
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


horde at nps.parcellsharp.net (2005-10-16 05:54) wrote:

I also experienced thisn (and other very weird behavior in import) recently
with CVS HEAD from about half a week ago.  However, when I tried to start
with a clean user to make simple reproduction steps, I found I couldn't
reproduce it easily.  There clearly is some type of non-obvious
circumstances that cause this behavoir.  I will continue trying to find
those.

If it helps, the user who was having the problems was a user who started out
with a fresh clean database and had >2000 entries imported via SyncML.