[kronolith] bug in add/edit recurrent event, takes all apache ressources

[Chuck Hagenbuch]

Quoting Benoit St-Andre <ben at benoitst-andre.net>:

> In Kronolith fresh HEAD from cvs, when you add or edit a recurrent event, if
> you chose to add/edit an event...
> -with a pattern "Monthly: Recurs every [input box] month(s) on the same
> weekday" or
> - with a pattern "Yearly: Recurs every [input box] year"
>
> - while putting a 0 (ZERO) or an empty value in the input box, and then save
> the event...
>
> The page never arrives and the httpd process starts taking 100% of 
> the CPU and
> stays there forever (until you kill it). Very funny behaviour, (I'm suprised
> that php_max_execution_time is not reached ever...) having to kill processes
> and restart the web server :-)

I've changed CVS to disallow recur_intervals of less than 1.

-chuck

--
"Regard my poor demoralized mule!" - Juan Valdez