[kronolith] (no subject)

[Ed Coates]

> If the backend were PostgreSQL (or maybe something other than MySQL)
> there was a bug fixed in CVS yesterday that caused the problem of
> setting events to midnight.  However it shouldn't effect MySQL.
>
> You might try setting your log level to LOG_DEBUG and see if you get any
> better messages in your horde log.

I'd have to beg to differ with you there.  I'm running MySQL 4.0.2-alpha as my 
back end.  I'm trying to configure a recurring event every Friday for 9:30 AM 
to 10:30 AM.  I pick the correct start date/time and end start/date time.  In 
the pattern, I pick Weekly: Recurs every 1 week*s) on:  and check Fri.  I then 
pick the No end date under the Recur Until area and save it.

It doesn't set it to recur every Fri.  When I go back and edit it, in the Recur 
Until area, there is a date checked, and it's always Dec 31 2001, so it never 
recurs.  No matter how many times I edit it to have No end date, it always 
picks that option.  The only time that I can get it to recur, is when I 
actually pick a date in the future, and then it will recur until then.

Any fixes for this in sight?

Ed



-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/