Excellent!  Thank you guys so much for a quick response.  I greatly 
look forward to trying this out next chance I get.

Fixed. The problem was actually the countEvents() call that opens all 
calendars. Moving the open() call below that fixed this bug.

This patch corrects the calendar import problem in our environment.



I believe the $kronolith global variable gets clobbered at some point 
during the import loop, although I could not track it down to actual 
offending line of code. Moving the $kronolith->open(...) call into the 
import loop fixes the problem by restoring the target calendar name 
from the session variable just prior to constructing the new event 
instance.



The open(..) method appears to have some defensive code that will 
allow it to reuse an existing DB connection whenever possible, so I 
expect only a minor performance penalty.  While I admit this approach 
is a bit heavy-handed, such is the price of using globals.



Comments and feedback welcome.



Tom Evans

Tachometry

Reproduced

I think I have found the problem.  The problem happens for both CSV 
and iCal importing and the deal is that it always puts the new entries 
into the last calendar alphabetically, no matter what you choose to 
import to.  To reproduce, create a new calendar called "Active", which 
will sort first and try an import data to it.

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.

No feedback.

I can't reproduce this.

Our users are running into some odd behavior when importing vCalendars 
into Kronolith.  They'll create a new calendar, then import a 
vCalendar (exported from Netscape Calendar) to the calendar.  However, 
it will always assign the imported events to their original calendar.   
It doesn't matter if the "new" calendar is set to default or not, same 
behavior.