Event Repeat doesn't work correctly if the event to repeat are in the past.
killes@www.drop.org - July 20, 2007 - 12:07
| Project: | Event Repeat |
| Version: | 5.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
It seems to me that repetisions starting in the past aren't really supported. I get wrong results for the if I try them. Does anybody else experience this?
I am going to add a validation routine that prohibits using eventrepeat with start dates in the past.
#1
According to hunmonk this is expected behaviour since the calendar map is only present from "today" on. The missing check on validation is thus a bug that needs fixing.
#2
this appears to be fixed.
#3
#4
Repeating events starting in the past do not work at all, just adding validation is not fixing the issue.
This should not be closed, simply because people will look for this issue and they will keep creating new duplicate issues.
Not sure why this cannot be fixed, or if this will ever be fixed (it does not seem likely), but this issue, or a similar one, should stay open.
#5
With the way that eventrepeat was written, I think the main issue with allowing events in the past like this is performance. The original code was meant to trim the previous dates out of the database to help lighten the load for when the database looks into the future and there are a ton of events.
Future versions might be able to account for this, but I don't see it happening for this version. Mainly because eventrepeat has other performance issues as is.
I agree that there might be an issue in that the interface does not clue you in to this limitation, however. If we addressed that for this version, would it answer your concerns?
#6
Improving the interface would definitely help.
#7
Updating the Title.