| Summary | 30 days Months and recurring events |
| Queue | Kronolith |
| Queue Version | 2.1.5 |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | jan (at) horde (dot) org |
| Requester | ufs (at) ufsoft (dot) org |
| Created | 04/04/2007 (6667 days ago) |
| Due | |
| Updated | 04/17/2007 (6654 days ago) |
| Assigned | 04/09/2007 (6662 days ago) |
| Resolved | 04/17/2007 (6654 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Assigned to Jan Schneider
State ⇒ Resolved
New Attachment: krono4.png
Please let me know if you need any more info.
New Attachment: krono3.png
May 4th, still, 2 full days, repeating every day.
New Attachment: krono2.png
ocupies all day, recurrs every day and ends on May 1st, which should
ocupy 2 full days.
From this screenshot you see that it actually ocupies 3 full days.
New Attachment: krono1.png
where you got that idea.
month you select, you always have 31 days, I'm fine by that because it
would envolve some of logic to switch the days range based on the
month seleted.
you did. If you created an event with a duration long enough to take
it into a second day (9pm to 1am for example), and set it to recur
twice, then of course it'll show up on a third day. But I have no
idea if that's what you did or not.
Priority ⇒ 1. Low
State ⇒ Feedback
where you got that idea. You need to be a bit more precise about what
you did. If you created an event with a duration long enough to take
it into a second day (9pm to 1am for example), and set it to recur
twice, then of course it'll show up on a third day. But I have no idea
if that's what you did or not.
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ 30 days Months and recurring events
Queue ⇒ Kronolith
State ⇒ Unconfirmed
ended on May 1st, I got a 3 day recurring event from April 30th until
May 2nd.
I guess this is due to the fact that parts of kronolith assume that
every month has 31 days.
For me, this is a HUGE bug.
Regards,
Pedro Algarvio, aka, s0undt3ch